brainstorming

Guides collaborative design dialogue to produce approved feature specs before implementation.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill brainstorming-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/brainstorming
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill brainstorming-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding new features without a validated design, leading to unexamined assumptions, scope creep, and wasted implementation effort. This Skill enforces a structured brainstorming workflow that turns rough ideas into reviewed, approved design specs before any code is written. ## Core Features & Use Cases - Guided Discovery Dialogue: Explores project context, then asks one clarifying question at a time (preferring multiple-choice) to pin down purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 design approaches with tradeoffs and a clear recommendation before committing. - Spec Generation & Self-Review: Writes the approved design to docs/specs/YYYY-MM-DD-<topic>.md, commits it to git, and runs a self-review for placeholders, contradictions, and ambiguity. - Use Case: Before building a new Flutter feature with Firestore storage, use this Skill to explore the data model, error handling, and testing strategy with your team lead, then hand off an approved spec to the planning phase. ## Quick Start Ask the AI to brainstorm the design for your new feature idea before writing any specification or 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 writing code?▼

Start by exploring the existing project context, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The process proposes 2-3 approaches with tradeoffs, presents the design section by section for approval, and saves the result as a dated spec file in docs/specs.

What should a software design spec include?▼

A design spec should cover high-level architecture, components such as feature folders and data collections, data flow and data model, error handling, and a testing strategy. Each section should be scaled to complexity and approved before moving on.

Can I skip the design step for a simple feature?▼

No. The workflow treats 'it's simple, no design needed' as an anti-pattern because simple projects are where unexamined assumptions waste the most time. The design can be only a few sentences, but it must be presented and approved.

When should a feature request be split into multiple specs?▼

Split the request when it spans multiple independent subsystems, such as auth plus feed plus billing. Each sub-project gets its own spec, plan, and build cycle so each design stays focused enough for a single implementation plan.

What happens after the design spec is approved?▼

After the spec passes self-review and user approval, the workflow transitions to the writing-plans skill, which creates a detailed implementation plan. No other skills or implementation actions are invoked before that point.