Brainstorming

Process Flow

1. Explore context — understand the project, codebase, and constraints
2. Ask clarifying questions — one at a time, prefer multiple-choice
3. Propose 2-3 approaches — with trade-offs for each
4. Present design sections — get approval incrementally
5. Write design document — save to docs/superpowers/specs/
6. Perform spec self-review — check for placeholders, contradictions, scope issues
7. User reviews written spec — explicit approval required
8. Invoke implementation — only after approval

Key Principles

• One question per message to avoid overwhelming users
• Multiple choice preferred over open-ended questions
• YAGNI ruthlessly — remove unnecessary features
• Always explore alternatives before settling on one approach
• Simple projects still require design validation: "A todo list, a single-function utility, a config change — all of them"

Self-Review Checklist

After writing specs, verify:

• No placeholders or TODOs remain
• No internal contradictions
• Scope is appropriate
• No ambiguities that could be interpreted multiple ways