design-doc
Installation
SKILL.md
Design Doc
- Read the brief and any linked docs, code, or plans. Ask a question, one at a time with a recommended answer, only when a missing fact would change the design.
- Write
docs/<design-slug>/design.md, 1-3 pages, using the template below. Omit sections that don't apply. - Stop after writing. Don't continue into spec, plan, or implementation until the human confirms.
Rules
- Focus on decisions code won't explain later.
- Don't copy full schemas, APIs, or code unless the exact shape is central.
- Leave Status as Draft and Decision empty. Both are filled during review.
Template
# <Title>
**Status:** Draft | In review | Approved
**Author:** <name> **Date:** <date>