superspec:brainstorm

Convert ideas into proposal.md, design.md, and specs/*.md artifacts.

3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-brainstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: superspec:brainstorm
Source: https://github.com/HankLiu447/SuperSpec/tree/main/skills/brainstorm
Command: npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured ideation workflow that converts vague ideas into concrete design artifacts, reducing drift between concepts and implementation.

Core Features & Use Cases

  • Progressive four-phase flow: Explore → Propose → Design → Spec, guiding teams from exploration to testable specs.
  • Outputs: proposal.md, design.md, and specs/*.md to capture decisions and requirements.
  • Collaboration-ready: supports cross-functional input and documentation.

Quick Start

Announce the brainstorm intent, then start with Explore to gather context, questions, and constraints. Use the outputs to generate a proposal, a design, and specifications.

Frequently Asked Questions about superspec:brainstorm

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

FAQPage Schema
How do I turn vague product ideas into concrete specs?▼

To turn vague ideas into concrete specs, use a structured ideation workflow that enforces a four-phase process: Explore, Propose, Design, and Spec. This captures decisions and generates testable requirements, reducing drift between concepts and implementation.

What is the best way to structure brainstorming for new feature planning?▼

The best way to structure brainstorming for new feature planning is a progressive flow from exploration to testable specs. Start by gathering context and constraints, then generate a formal proposal, a design document, and specification files.

How does the Explore to Spec design workflow work?▼

The workflow works by guiding cross-functional teams through four phases: Explore to gather context, Propose to generate proposal.md, Design to create design.md, and Spec to output specs/*.md files, enforcing validation checks at each stage.

Can I use this structured ideation workflow for architecture changes?▼

Yes, you can use this structured ideation workflow for early-phase planning of architecture changes, process improvements, and new features. It supports collaboration-ready outputs to capture decisions across product teams.

What documents do I need for cross-functional product specification?▼

For cross-functional product specification, you need proposal.md to capture the initial proposal, design.md for design decisions, and specs/*.md files for detailed requirements. These artifacts reduce concept drift.