Agent skill · product strategy · aiskillstore
brainstorming
Transform rough ideas into detailed designs through structured dialogue. Use before implementation to refine requirements.
Why this skill is useful
Provides a structured approach to refining vague ideas into detailed designs, which the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Brainstorming & Design Refinement Transform rough ideas into validated designs through structured Socratic dialogue before any implementation begins. When to Use Starting a new feature with unclear requirements Exploring solution approaches Refining vague ideas into concrete plans Before writing any implementation code The Workflow Phase 1: Understanding 1. Review existing project context (files, docs, patterns) 2. Ask clarifying questions sequentially - one per message 3. Use multiple-choice when feasible (easier to answer) 4. Focus on: What is the purpose/goal? What are the constraints? What does success look like? Who/what is affected? Key rule: One question at a time - avoid overwhelming Phase 2: Exploring Options 1. Present 2-3 different approaches 2. Lead with your recommended approach 3. Explain trade-offs for each: 4. Discuss conversationally, not prescriptively 5. Be open to hybrid approaches Phase 3: Design Presentation 1. Break design into digestible sections (200-300 words each) 2. Validate incrementally after each section 3. Cover: Architecture overview Key components Data flow Error handling Testing approach 4. Remain open to revisions Key Principles YAGNI (You Aren't Gonna Need It) Ruthlessly eliminate speculative features: Ask If No → -------------------------------- ------------- Is this required for MVP? Cut it Does the user need this now? Defer it Are we guessing at requirements? Clarify first One Question at a Time Explore Before Committing Don't jump to the first solution. Consider: What's the simplest approach? What's the ideal approach (no constraints)? What could go wrong? How would this be solved differently in 5 years? Output: Design Document After validation, produce: Post-Design 1. Save design to docs/plans/YYYY-MM-DD-[feature].md 2. Commit the design document 3. Transition to implementation using writing-plans skill
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/brainstorming--9836fd