brainstorminglisted

Turn an idea into an agreed design before implementation — explore project context, ask clarifying questions one at a time, propose two or three approaches with trade-offs and a recommendation, present the design in sections for approval, and record the agreed design. Use when the user proposes a feature, component, behavior change, or project whose requirements or shape are not yet pinned ('let's build', 'I want to add', 'how should we approach'), or when one request bundles several independent subsystems and needs decomposition before any single design is refined. Design before code holds for small work too — a simple project gets a proportionally short design, not an exemption. Hands the agreed design to the planning tool that owns execution (keel for governed series, plan mode or your orchestrator otherwise). Not for work already specified to execution level, and not for discussion turns where the user is thinking aloud and wants assessment rather than artifacts.
grimaldost/craft-collection · ★ 2 · AI & Automation · score 68

Install: claude install-skill grimaldost/craft-collection

# Brainstorming Turn an idea into a design the user has agreed to, through dialogue — then hand it to planning. This is a **flexible** skill with one firm gate, stated once: implementation starts after the user approves a design. Small work gets a proportionally small design — a few sentences can be enough — rather than an exemption, because simple-looking projects are where unexamined assumptions cost the most rework. ## The flow 1. **Explore project context first.** Files, docs, recent commits — before asking the user anything they shouldn't have to repeat. 2. **Check scope before refining.** A request that bundles several independent subsystems (chat, billing, storage, analytics) gets decomposed first: what are the pieces, how do they relate, what order. Then design the first piece through the normal flow. Don't spend questions polishing details of something that needs splitting. 3. **Ask focused questions, one decision at a time.** One question per turn by default; for an expert user facing orthogonal decisions, batch a few into one turn via the host's question UI rather than forcing strict serialization. Multiple choice when it fits, open-ended when it doesn't. Aim at purpose, constraints, and success criteria. 4. **Propose two or three approaches** with trade-offs. Lead with the recommendation and the reasoning, not a neutral menu. 5. **Present the design in sections,** each scaled to its complexity — a few sentences when straightforw