reasoning-doctrine
SolidThe working method — how to think, stage, self-check, and hold alignment across long tasks without needing reminders. Use this skill on EVERY nontrivial task: analysis, planning, implementation, debugging, document work, reviews, or anything spanning more than a few tool calls or more than one response. Especially mandatory on long-running or multi-stage work, where drift is the primary failure mode. If a task has stages, this skill governs how you move through them.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- Ezra144israel
- Repository
- Ezra144israel/governed-agent-skills
- Created
- 1 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
reasoning
Use for reasoning discipline that applies underneath every domain competency and every stage: decomposing an ambiguous or underspecified request into facts/inferences/recommendations/open questions, deciding whether an unknown is genuinely material enough to ask a required question, attaching High/Medium/Low confidence labels to a non-trivial claim in a handoff artifact (design.md, planning.md, a competency edit, a code review), running the self-critique pass before handing work to the next stage or role, or turning an observed mistake into a durable knowledge-base change. Load this alongside whichever domain competency or stage skill the current work calls for — it does not replace `architecture`, `business-analysis`, or any other domain competency, it underlies all of them.
reasoning-balance
Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.
sequential-thinking
Structured reasoning harness for problems where shallow thinking fails or hallucination is costly. Use whenever a question requires multi-step reasoning, involves competing hypotheses, has multiple interacting components, or carries irreversible consequences. Activate for debugging with unclear root causes, intermittent or multi-component issues, incident post-mortems, choosing between multiple valid approaches, architecture or design tradeoffs, causal chain analysis, high-stakes decisions, and any task where the first plausible answer is suspiciously easy. Provides reasoning modes (abductive, counterfactual, first-principles, inversion, and more), grounding techniques against confabulation, adversarial self-checks, root-cause playbooks, and automatic multi-approach synthesis (independent angles run in parallel and compared) — all through the `mcp__sequential-thinking__sequentialthinking` tool. Skip for trivial lookups, obvious fixes, and single-step questions.