dvy1987/agent-loom / .agents/skills/deep-thinking
deep-thinking
VerifiedOrchestrate one or more thinking frameworks to work through any problem, decision, document, or idea rigorously. Diagnoses which frameworks fit — inversion, pre-mortem, assumption-mapping, socratic, adversarial-hat — then guides the user through them in the right sequence. Load when the user asks for deep thinking, says "help me think through this properly", "apply your best thinking frameworks", "I need to think carefully before deciding", or "what thinking tools should I use here". Also the entry point for any complex problem where the right framework is unclear. Covers product decisions, engineering tradeoffs, personal decisions, strategy, creative challenges — any domain.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.5 KB |
| references/examples.md | markdown | 2.8 KB |
references/examples.md
View on GitHub# Deep Thinking — Full Worked Examples
Skill: `deep-thinking` | Enriched from SKILL.md (improve-skills pass, SKIP_RESEARCH).
## Example 1 — Documented workflow
**Input:** I need to decide whether to hire a full-time community manager or outsource it. I've been going back and forth for weeks.
**Output:**
```
Going back and forth usually means the decision criteria are unclear, not that the options are equal. I'll start with Socratic to find what's actually blocking you — then we can pressure-test whichever direction becomes clearer.
[Runs socratic — after 3 questions reveals: the user is uncertain whether community will be a core motion or a side feature, which makes the resourcing question unanswerable]
The real question isn't who manages community — it's whether community is central to your retention strategy or a nice-to-have. That's what needs to be decided first.
Shall I run inversion on "community as core retention strategy" to help you think that through? Or would you rather map the assumptions behind each option?
```
## Example 2 — Step-by-step execution
**Input:** "Run `deep-thinking` on [concrete task]"
**Agent actions:**
1. Diagnose
2. Name the Framework(s) and Why
3. Run the Primary Framework
4. Check: Is More Needed?
5. Run Secondary Framework (if needed)
6. Synthesise
**Impact Report shape:**
```
Deep thinking session: [problem/decision/document]
Frameworks used: [list]
Core insight: [the main thing this session revealed]
Hidden assumption/question exposed: [if any]
Concrete next action: [what to do now]
```
## Example 3 — Anti-skip (rationalization defense)
**Input:** Agent tries to skip a gate
| Excuse | Reality |
|---|---|
| "I already thought about it" | Deep-thinking forces explicit framework choice, not vibes. |
| "One framework is enough" | Wrong frame applied confidently is worse than diagnosing first. |
| "This doesn't need deep analysis" | Router exists because mis-framed problems waste the wrong skill. |
| "More thinking = paralysis" | Output must end with one concrete next action. |
## Example 4 — Gotcha application
**Input:** Task hits a non-obvious edge case
**Apply:**
- **Diagnosis is the most important step.** Wrong framework for the problem wastes time and produces shallow insight. Invest in Step 1.
- **Socratic and adversarial-hat don't combine well.** Socratic builds up; adversarial tears down. Use one per session unless a specific finding calls for the other.
- **Pre-mortem works best just before commitment.** If the decision is already made, use `adversarial-hat` instead.
- **If the user is emotionally attached to their plan**, lead with `socratic` to surface their assumptions through questions rather than `adversarial-hat` which can feel like an attack.
---
See `SKILL.md` for hard rules and verification checklist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |