About reason
Reason is a temporary, stateless consultation skill for agent work involving judgment or uncertainty. It examines a bounded claim or decision and returns a brief disposition, while leaving implementation and acceptance to the owning task.
Key features
- 01Stateless, artifact-free consultations
- 02Checkpoints for consequential judgment
- 03Decide, challenge, and ask branches
- 04Tests assumptions and opposing arguments
- 05Returns a brief disposition without approval
Use cases
- 01Examining a proposal before choosing an approach
- 02Reassessing after a failure or direction change
- 03Identifying evidence gaps before reporting a result
- 04Surfacing a user-owned decision that blocks progress
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ akshay-diwadkar/ first-four-hours --skill reasonAfter installing, type/reasonin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/ask.mdchallenge.mdcheckpoint-trace.mddecide.mddelegation-protocol.mdresults.mdDetails
From the project READMEReason
Temporary, stateless, and artifact-free: Reason never mutates any state, gives no mutation or domain authority to itself, and outputs only the consultation result, with no score, confidence, or vote. The owning task keeps artifacts, acceptance, completion, and implementation decisions.
Checkpoints
Applicability follows open judgment, uncertainty, and consequence, never task size or file count. Work that chooses an approach, weighs evidence or tradeoffs, or claims an outcome no mechanical check settles must consult Reason before committing to an approach, after a failure or direction change, and before presenting the result. A failed tool, probe, identity check, or seal the work relies on is a failure. Considering consultation, or affirming untested, is not consultation; confidence or one plausible move is no exemption, because owners cannot see their own blind spots. Work with nothing left to judge, such as a rote edit, routine technical repair, or applying a decision-complete plan, skips checkpoints; a plan contradiction returns to the planning owner.
Each consultation is one bounded pass scaled to consequence: the current goal, proposal, or result; its authority and evidence; and the action it could change. On a non-trivial decision, state the strongest opposing argument, test blind spots, and verify every load-bearing assumption. It ends with a visible one- or two-line result naming the examined claim or decision, the risk tested, and one disposition: material objection, missing evidence, needed user input, or no material concern; never manufacture criticism or persist the line. Reason explains what to reconsider and why; the owner weighs it and fixes supported gaps. No recursion, panels, or automatic call chains. Each consultation reads Results for what is non-trivial, where the line and results go, and what an open disposition requires. Owners report checkpoints per Checkpoint trace.
Branches
Choose the smallest branch owning the concern by judgment; branches may reclassify internally. Read the branch reference on entry; it holds the user-facing result shape.
- decide: no defensible next move exists because goal, evidence, conflict, cause, options, assumptions, or failure remain unresolved: decide details.
- challenge: a concrete proposal or result exists: challenge details, which says when to brief a fresh challenger.
- ask: progress depends on a material user-owned fact, choice, preference, policy, permission, risk tolerance, scope, authority, or operational rule that evidence and bounded exploration cannot derive: ask details.
No result is approval or proof of correctness.