brainstorm

Convert rough ideas into executable specifications with structured spec files.

107|15|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill brainstorm-rhuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/rhuss/cc-superpowers-sdd/tree/main/skills/brainstorm
Command: npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill brainstorm-rhuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you refine vague ideas into clear, formal, and executable specifications, preventing ambiguity and rework later in the development cycle. It ensures that "what" needs to be built is crystal clear before "how" it's built.

Core Features & Use Cases

  • Collaborative Refinement: Guides you through questions to clarify purpose, constraints, and edge cases.
  • Approach Exploration: Proposes 2-3 alternative solutions with trade-offs.
  • Formal Spec Generation: Creates a structured, executable specification (e.g., specs/features/new-feature.md) that becomes the single source of truth.
  • Use Case: You have a rough idea for "user authentication." This skill will ask about types (OAuth, email/password), session management, and MFA, then generate a detailed spec for your chosen approach.

Quick Start

To start refining a new feature idea, simply say: I want to add user authentication to my app.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a rough product idea into a detailed specification?

Specification writing converts vague concepts into formal, executable specs through guided questioning about purpose, constraints, and success criteria. This Skill walks you through collaborative refinement to produce a structured spec document that serves as the single source of truth before development begins.

What should a product specification include?

A complete specification covers functional and non-functional requirements, success criteria, edge cases, dependencies, and alternative approaches with trade-offs. This Skill generates specs with these sections to ensure alignment with your project and prevent ambiguity during implementation.

When should I write a spec before building a feature?

Specifications are most valuable at project inception or feature kickoff, especially in collaborative sessions where multiple stakeholders need alignment. Writing specs upfront prevents rework and clarifies what must be built before engineering decisions about how to build it.

How do I compare different approaches to solving a problem?

This Skill proposes 2-3 alternative solutions with their trade-offs during the refinement process, helping you evaluate options like authentication methods, session management strategies, or architectural patterns before committing to one approach.

Can I use this for requirements gathering in collaborative sessions?

Yes. The Skill is designed for collaborative refinement, asking clarifying questions one at a time to build consensus on purpose, constraints, and edge cases across team members, producing a shared spec that aligns everyone before development starts.

What happens after I finish creating a specification?

After specification generation, you can optionally create implementation notes that translate the spec into development tasks. The spec becomes your project's reference document, and developers use it to guide code design and testing strategies.