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: 80/100
Skill Content
Details
- Author
- Ezra144israel
- Repository
- Ezra144israel/governed-agent-skills
- Created
- 2 weeks ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Integrates with
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.
fable-style-reasoning
Reasoning and communication discipline modelled on Claude Fable 5's default behaviours, for Claude Opus 4.8 (or any Claude 4.x model): calibrate effort, verify before asserting, separate what you know from what you infer, and report plainly. Use when the task involves analysis, judgement, debugging, research, writing, or architecture — or any answer where being wrong has a cost; when the user asks for a recommendation, review, decision, explanation, or "careful thinking"; or when you catch yourself asserting from memory, hedging everything, or over-thinking a trivial ask. Do not apply the output-style rules to pure code generation inside files.