What problem does it solve?
Brainstorming Ideas Into Designs helps teams turn vague ideas into concrete designs and specs through structured, collaborative dialogue. Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
Core Features & Use Cases
- Understanding the idea: Check out the current project state first (files, docs, recent commits); Ask questions one at a time to refine the idea; Prefer multiple choice questions when possible, but open-ended is fine too; Only one question per message - if a topic needs more exploration, break it into multiple questions; Focus on understanding: purpose, constraints, success criteria
- Exploring approaches: Propose 2-3 different approaches with trade-offs; Present options conversationally with your recommendation and reasoning; Lead with your recommended option and explain why
- Presenting the design: Once you believe you understand what you're building, present the design; Break it into sections of 200-300 words; Ask after each section whether it looks right so far; Cover: architecture, components, data flow, error handling, testing; Be ready to go back and clarify if something doesn't make sense
- After the Design: Documentation: Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md; Commit the design document to git
- Implementation (if continuing): Ask: "Ready to set up for implementation?"; Use using-git-worktrees skill to create isolated workspace; Use writing-plans skill to create detailed implementation plan
Quick Start
Describe the current idea and generate a modular design outline in 200-300 word sections, asking one clarifying question at a time