brainstorming

Guides collaborative dialogue to turn ideas into approved design documents before implementation.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill brainstorming-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Avistian/nba/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/Avistian/nba --skill brainstorming-avistian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding without clarifying requirements, leading to wasted work on unexamined assumptions. This Skill enforces a structured discovery process that explores user intent, constraints, and design alternatives before any implementation begins. ## Core Features & Use Cases - Structured Discovery: Explores project context, then asks clarifying questions one at a time to understand purpose, constraints, and success criteria. - Design Exploration: Proposes 2-3 approaches with trade-offs and a recommendation, then presents the design in sections for incremental approval. - Design Documentation: Writes the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md, commits it to git, and hands off to the writing-plans skill. - Use Case: Before building a new feature, use this Skill to interview yourself about requirements, compare architectural options, and produce an approved design doc that implementation can follow. ## Quick Start Ask the assistant to brainstorm the design for your new feature before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm a feature design before coding?▼

Start by exploring the current project context, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The process proposes 2-3 approaches with trade-offs and presents the design in sections for your approval before any code is written.

What is the best way to gather software requirements?▼

Ask one question at a time, preferring multiple-choice formats when possible, and focus on purpose, constraints, and success criteria. This avoids overwhelming stakeholders and surfaces assumptions that open-ended interviews often miss.

Does this design process apply to small or simple projects?▼

Yes, every project goes through the process regardless of perceived simplicity, including single-function utilities and config changes. The design can be just a few sentences for simple work, but it must still be presented and approved.

Where are approved design documents saved?▼

Validated designs are written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git. After documentation, the workflow transitions to the writing-plans skill to create the implementation plan.

When should I skip brainstorming and go straight to implementation?▼

Never within this workflow. The skill enforces a hard gate that blocks invoking implementation skills, writing code, or scaffolding projects until a design has been presented and explicitly approved by the user.