← ClaudeAtlas

brainstorminglisted

Explore requirements and compare design alternatives before substantial or ambiguous feature development. Use when the user asks to brainstorm a feature, define requirements, choose architecture, or plan a non-trivial behavioral change. Do not use for small, well-specified fixes or routine configuration changes.
thestratcore/My-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill thestratcore/My-skills
# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context, then ask only questions whose answers materially affect the design. Present a design and obtain approval before implementing substantial or ambiguous changes. Skip this workflow for small, well-specified fixes and routine configuration changes. ## Checklist You MUST create a task for each of these items and complete them in order: 1. **Explore project context** — check files, docs, recent commits 2. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria 3. **Propose 2-3 approaches** — with trade-offs and your recommendation 4. **Present design** — in sections scaled to their complexity and obtain approval 5. **Write a design document when useful** — use the repository's preferred location 6. **Spec self-review** — check placeholders, contradictions, ambiguity, and scope 7. **Transition to implementation** — create a plan appropriate to the task ## Process Flow ```dot digraph brainstorming { "Explore project context" [shape=box]; "Ask clarifying questions" [shape=box]; "Propose 2-3 approaches" [shape=box]; "Present design sections" [shape=box]; "User approves design?" [shape=diamond]; "Write design doc" [shape=box]; "Spec self-review\n(fix inline)" [shape=box]; "User reviews spec?" [shape=diamond]; "Invoke writing-plans