| name | brainstorming |
| description | Explore user intent, requirements, and design before implementation. Recommended before creative work such as new features or component design. |
Brainstorming Ideas Into Designs
Goal
Clarify requirements and produce a design before jumping to code. Reduces wasted work from unexamined assumptions.
Design Review
Present a design and get user feedback before implementation. The design can be brief for simple tasks. For trivial changes (rename, typo fix), skip directly to implementation.
Checklist
- Explore project context — check files, docs, recent commits
- Ask clarifying questions — one at a time; prefer multiple-choice over open-ended
- Propose 2-3 approaches — with trade-offs; lead with your recommendation
- Present design — scale detail to complexity; check after each section
- Save design doc —
docs/plans/YYYY-MM-DD-<topic>-design.md
- Transition — invoke writing-plans skill to create implementation plan
Guidelines
- Scale sections to complexity — a few sentences if straightforward, more if nuanced
- Cover: architecture, components, data flow, error handling, testing
- Apply YAGNI — remove unnecessary features from designs
After Approval
- Save the design to
docs/plans/YYYY-MM-DD-<topic>-design.md
- Commit the design document
- Invoke writing-plans to create the implementation plan
