brainstorming

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill brainstorming-viniciuscs84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/viniciuscs84/sdd-toolkit/tree/main/skills/brainstorming
Command: npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill brainstorming-viniciuscs84

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Jumping straight from an idea to code leads to unexamined assumptions, scope creep, and wasted work. This Skill enforces a structured design phase where requirements are clarified, approaches are compared, and a written spec is approved before any implementation begins. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents the design in sections for incremental approval. - Spec Writing and Review Gates: Writes the validated design to a dated spec file, runs a self-review for placeholders, contradictions, ambiguity, and scope, then requires explicit user approval before planning. - Browser-Based Visual Companion: Serves mockups, wireframes, and side-by-side layout comparisons in a local web page so users can click to select visual options during brainstorming. - Use Case: Before building a new feature, use this Skill to refine the idea through dialogue, compare architecture options, and produce an approved design document that feeds directly into implementation planning. ## Quick Start Ask the agent to brainstorm the design for your new feature before writing any code, and answer its clarifying questions one at a time.

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 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, presents the design in sections for approval, and writes a spec document before any implementation begins.

What should a software design spec document include?

A design spec should cover architecture, components, data flow, error handling, and testing, with each section scaled to its complexity. It must avoid placeholders, internal contradictions, and ambiguous requirements, and stay focused enough for a single implementation plan.

Can I review UI mockups in a browser during brainstorming?

Yes, the visual companion starts a local server that serves HTML mockups, wireframes, and side-by-side layout comparisons in your browser. You click to select options, and your choices are recorded as events the agent reads on its next turn.

Does every project need a design phase, even simple ones?

Yes, the process applies to every project regardless of perceived simplicity, including single-function utilities and config changes. For truly simple projects the design can be just a few sentences, but it must still be presented and approved before implementation.

What happens if a project is too large for one spec?

Oversized projects are decomposed into independent sub-projects with defined relationships and build order. Each sub-project then goes through its own brainstorm, spec, plan, and implementation cycle starting with the first one.