brainstorming

Refines feature ideas into validated design documents through structured dialogue.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/macintorsten/aurapod --skill brainstorming-macintorsten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/macintorsten/aurapod/tree/main/.github/skills/brainstorming
Command: npx skills add https://github.com/macintorsten/aurapod --skill brainstorming-macintorsten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into implementation without clarifying requirements leads to wasted effort and misaligned features. This Skill guides a collaborative exploration of user intent, requirements, and design before any code is written. ## Core Features & Use Cases - Guided Requirement Discovery: Asks one question at a time, preferring multiple choice, to clarify purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, validating each section before continuing. - Use Case: Before adding a new playlist feature to a web app, use this Skill to explore user intent, compare implementation approaches, and produce a committed design document in docs/plans/. ## Quick Start Ask the AI to brainstorm and design a new feature before implementing it, describing your rough idea in one sentence.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature idea into a design document?▼

Start by reviewing the current project state, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The design is presented in 200-300 word sections for validation, then written to docs/plans/ and committed to git.

When should I brainstorm before writing code?▼

Brainstorm before any creative work: creating features, building components, adding functionality, or modifying behavior. Clarifying requirements and comparing approaches upfront prevents rework from misunderstood intent.

How does the design review process work?▼

The design is broken into sections of 200-300 words covering architecture, components, data flow, error handling, and testing. After each section you confirm whether it looks right, and the process loops back to clarify anything that does not make sense.

What happens after the design is approved?▼

The validated design is written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git. If you continue to implementation, an isolated git worktree is created and a detailed implementation plan is produced.

What are the limitations of a dialogue-based design process?▼

The process depends on your answers to converge, so vague or shifting requirements slow it down. It also produces a design document only; actual implementation requires separate planning and execution steps.