think
Strategic analysis, adversarial validation, executive council debate, and discovery mode for complex decisions
Files5
View on GitHubSKILL.mdskills/think/SKILL.md
GitHubThink
Use Think for high-stakes reasoning. Use workspace context, but do not flood the main session. Subagents may explore alternatives or objections and must return bounded summaries.
Modes
| Mode | Use when |
|---|---|
| Strategic analysis | The user asks for analysis, tradeoffs, or recommendation |
| Validation | The user asks what could go wrong or to stress-test |
| Executive council | The user wants multi-perspective debate |
| Discovery | The problem is ambiguous or needs non-obvious angles |
| Deep analysis | The user explicitly needs a full chain of analysis |
If discovery requires a dedicated bisociation engine, route to skills/ideate/.
Rules
- State the framework and why it fits.
- Separate evidence, assumptions, risks, and recommendation.
- Use internal context when relevant, but cite uncertainty.
- Do not persist analysis unless the user asks or the workflow requires a saved artifact.
References
manifesto.mdreferences/analyze.mdreferences/council.mdreferences/legacy-full-protocol.md