← ClaudeAtlas

planlisted

Break work that is already decided into atomic issues someone can pick up in whatever order the dependencies allow, with the sequencing reasoning attached. Use it when the approach is settled and the open question is execution shape: "break this into issues", "file issues for this design", "what order should we do these in?", "this is too big for one PR, split it up", "what tasks do we need?", "how many issues is this?", or an accepted design handed over with "let's start building" — an agent that picks its own starting point ships the pieces in an order that does not build. Do NOT use it when the feature itself is not worked out and the requirements and approach are still open; that whole run is `/scope`, which calls this as its last hop. Do NOT use it to sequence FEATURES across an initiative rather than issues inside one (`/roadmap`), or to run the resulting plan (`/execute`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh plan 2>&1 || true` @.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