autoplan

# Autoplan ## Contract | Field | Bound contract | |---|---| | Trigger | The user runs `/autoplan` on a plan or idea. | | Authority | Reversible local: writes only the amended plan, the task JSONL ledger at `tasks/autoplan-ledger.jsonl`, and TODO updates; rollback is discarding those local artifacts. No remote mutation. | | Side effect | Writes the amended plan, appends tasks to `tasks/autoplan-ledger.jsonl`, and updates TODOs. | | Done | The final approval gate presents an amended plan and aggregated implementation tasks with stable IDs. | ## Inputs Required: a plan or idea to develop, supplied as a file path or inline text. Optional: an existing `tasks/autoplan-ledger.jsonl` to extend. If absent, create one. ## Ledger destination and overwrite policy The task ledger lives at `tasks/autoplan-ledger.jsonl`. When the file does not exist, create it. When it exists, append new tasks to the end; never overwrite or truncate existing entries. Each run appends only the tasks it produces. This preserves prior runs and makes the ledger append-only across invocations. ## Task ID generation Each task gets a deterministic ID formed from the reviewing phase prefix and a zero-padded sequence number within that phase: - CEO review: `CEO-01`, `CEO-02`, ... - Design review: `DES-01`, `DES-02`, ... - DX review: `DX-01`, `DX-02`, ... - Engineering review: `ENG-01`, `ENG-02`, ... Sequence numbers start at `01` within each phase and increment in the order tasks are identified. IDs are s...