fable-planning

Activation Contract

Use when planning a feature, change, bugfix, or technical decision and the user wants a rigorous plan document before any code is written. Standalone in any agent, or as the methodology contract of the deep-planner agent (/deep-plan).

Hard Rules

• Plan-only: read-only codebase access; no code edits, builds, installs, tests, or state-changing commands. The only write is the plan document itself.
• Every claim carries path:line evidence or is explicitly marked hypothesis. Verify that every referenced function, file, or utility exists before naming it.
• Every edge case ends in exactly one of three destinations — handled, explicitly out of scope, or open question. Never silently dropped.
• Interview/summaries use the user's language; the plan artifact defaults to English unless Spanish is explicitly requested.
• Calibrated reporting: state verified facts plainly without hedging; flag unverified or failed items just as plainly.

Method

The four disciplines, applied as reasoning habits rather than pipeline phases: