← ClaudeAtlas

designlisted

Choose how something gets built and write the reasoning down: decompose it into the questions that actually have to be answered, weigh the options for each, and land a technical approach on a page. Reach for it when the requirements are already settled — an accepted PRD exists, or the feature is specified and the open question is pure architecture: "how should this talk to the existing cache?", "what's the migration path off the old schema?", "we have the PRD, now what?", "refactor the auth layer", "why is this slow and what do we do about it?". An agent that starts editing files instead has picked an approach without anyone seeing what it was picked over. Do NOT use it when the requirements are NOT settled and the feature still has to be worked out — that is `/scope`, which runs this as one hop and decides per feature whether a separate design survives. Do NOT use it for one named either-or choice (`/decision`), for requirements (`/prd`), or for a question with no options on the table yet (`/explore`).
tsukumogami/shirabe · ★ 0 · Web & Frontend · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh design 2>&1 || true` @.claude/shirabe-extensions/design.md @.claude/shirabe-extensions/design.local.md # Design Documents Design documents capture HOW to build something -- the technical approach, trade-offs considered, and architecture chosen. They complement PRDs (which capture WHAT and WHY) and are the input for /plan (which breaks designs into issues). **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Durable. Stays in `docs/designs/` after completion. DESIGN is durable because the architectural decisions captured at DESIGN-Accepted time are the audit trail of how the implementation was chosen. Future readers asking why a particular architecture was selected need the DESIGN to remain in place; Current-state designs move to docs/designs/current/ but stay on disk. ## Structure ### Frontmatter Every design doc begins with YAML frontmatter: ```yaml --- status: Proposed problem: | 1 paragraph: what's broken or missing, who it affects, why now. decision: | 1 paragraph: chosen approach and key design elements. rationale: | 1 paragraph: why this approach, what trade-offs were weighed. --- ``` All four fields required. Use literal block scalars (`|`). Frontmatter status must match the Status section in the body -- agent workflows parse frontmatter to determine lifecycle state, so divergence causes silent errors. The frontmatter provides a self-containe