planlisted

@.claude/shirabe-extensions/plan.md @.claude/shirabe-extensions/plan.local.md # Plan Skill Plans turn accepted designs into implementable work. They define the decomposition strategy, issue sequencing, and dependency graph that guide implementation through /work-on. When planning a roadmap, the output is planning issues (one per feature) rather than code-level issues. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Working. Completion condition: the work-on cascade verifies the PLAN-Active state's terminal contract and finalizes the chain. The lifecycle states are `Draft -> Active -> Done -> DELETED`, mirroring the working-artifact lifecycle template established in `docs/designs/current/DESIGN-lifecycle-draft-ready-discipline.md`. **Deleted by:** the work-on cascade's PLAN deletion step. The PLAN file is removed from disk in the same atomic finalization commit that transitions BRIEF/PRD to Done and DESIGN to Current. ## PLAN Doc Structure Plans live at `docs/plans/PLAN-<topic>.md`. See the full specification at `references/quality/plan-doc-structure.md`. Quick summary of required sections: 1. **Status** -- Draft, Active, or Done 2. **Scope Summary** -- 1-2 sentences on what the plan covers 3. **Decomposition Strategy** -- walking skeleton vs horizontal, with rationale 4. **Issue Outlines** -- structured outlines in single-pr mode 5. **Implementation Issues** -- issue table with links in multi-pr mode 6. *