planslisted

# Plans Keep a compact Plan Capsule, not the planning transcript, for material work. ## Plan Capsule ```text PLAN <id>: DRAFT | CHALLENGE-READY | FINAL AS OF <latest operator instruction accounted for> DEPTH: LIGHT | STANDARD | DEEP ASKED <operator's words that define the outcome> GOAL <accepted restatement> DELIVERABLE <what will exist> PLAN 1. <step with a checkable completion condition> 2. <step with a checkable completion condition> DONE <smallest observable acceptance condition> ``` Add `SOURCE HOME`, `BOUNDARIES`, or `OPEN` only when they carry load-bearing information. Copy `ASKED` from the operator. A continuation (`proceed`, `yes`) keeps `ASKED` and advances `AS OF`. A changed outcome replaces `ASKED`, updates the plan, and is read back. ## Readback Show the full current capsule when a load-bearing part of the plan changes, before challenge, on restore, and before final closeout. Append only applicable temporary sections: ```text CHANGED - <changed plan state> ADDED - <new agent-added scope or requirement> DROPPED - <operator-requested item that disappeared or changed meaning> ``` Do not persist those temporary sections after the operator has seen them. ## Depth and challenge - `LIGHT`: bounded, familiar, reversible work. No challenge by default. - `STANDARD`: several meaningful decisions or moderate uncertainty. Challenge when a load-bearing question remains, the operator asks, or error cost warrants it. - `DEEP`: architecture, broad blast radius,