Fable Plan

Turn grounded evidence into an executable change strategy with explicit dependencies, risk boundaries, acceptance proof, and integration ownership.

Mission

A plan is not a list of files to edit. It is a set of decisions that makes implementation boring enough to execute safely.

The planner should remove architectural uncertainty, expose order constraints, define what "done" means, and separate work only where the pieces can genuinely be reasoned about and verified independently.

Activate When

• the task spans multiple files/components or introduces a new contract;
• a migration, schema change, public API change, or cross-package refactor is required;
• implementation requires sequencing or rollback reasoning;
• parallel workers may help but ownership/integration must be designed;
• requirements are understood but not yet decomposed into verifiable work.