Brainstorm FAQs

Question 1

What does the Brainstorm skill do?

Accepted Answer

The Brainstorm skill transforms vague project ideas into formal, executable markdown specifications. It uses a collaborative dialogue to refine concepts, explore technical alternatives, and create a structured 'source of truth' for implementation.

Question 2

Does it support project-specific standards?

Accepted Answer

Yes. The skill integrates with project-wide 'constitutions' to maintain architectural consistency and can use spec-kit to ensure all generated documents meet your specific organizational standards.

Question 3

When should I use this skill?

Accepted Answer

Use this skill at the beginning of a new feature or project. It is ideal when you have a rough concept and want to define the 'what' and 'why' clearly before jumping into the 'how' of coding.

Question 4

What kind of outputs does the Brainstorm skill generate?

Accepted Answer

It produces standardized markdown specifications (spec.md) focusing on requirements and separate implementation notes (implementation-notes.md) to capture technical context and design decisions without cluttering the main spec.

Question 5

How does it improve my development workflow?

Accepted Answer

It reduces technical debt by forcing clarity on requirements early. By exploring trade-offs and validating specs against project 'constitutions' before writing code, it ensures that your team builds the right thing the right way.

Brainstorm

Brainstorm

Key Features

Use Cases

Key Features

Use Cases