reasoning-doctrine

Solid

The 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.

AI & Automation 16 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Reasoning Doctrine This file exists because the default failure modes on long tasks are known: drift from the original objective, silent scope mutation, answering before checking, declaring done before verifying, and needing the operator to re-issue reminders. Every mechanism below targets one of those. Follow them mechanically — the discipline must come from you, not from the operator. ## Progressive loading This file is the resident core: the mechanisms that fire on nearly every task. Three situational bodies live in a `references/` directory **alongside this file, in this skill's own directory**, and are read when their trigger fires, not before. Resolve each path relative to wherever this SKILL.md was loaded from: | Read | When | |---|---| | `references/escalation-and-retries.md` | any step comes back wrong, a tool fails, or confidence is degrading across attempts | | `references/decomposition-and-delegation.md` | work is being split into steps for another executor, a subagent, or a dispatch | | `references/failure-patterns.md` | a failure tell fires, a correction lands, or you are diagnosing your own process | Reading a reference is cheap; reading all three unprompted is the exact over-loading this structure exists to end. Context is a finite resource with diminishing marginal returns — every resident token spends attention budget whether or not it is relevant to the task in hand. ## Doctrine priority when rules conflict The mechanisms here will sometimes pull a...

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

Web & Frontend Listed

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.

0 Updated 3 weeks ago
BhangeeF16
AI & Automation Listed

reasoning-balance

Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.

1 Updated 5 days ago
ihabkhaled
AI & Automation Listed

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.

2 Updated 4 days ago
stealth-factory