01-brainstorm

Convert ambiguous requests into approved requirements artifacts through structured multi-round dialogue.

29|2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/leing2021/super-pi --skill 01-brainstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 01-brainstorm
Source: https://github.com/leing2021/super-pi/tree/main/skills/01-brainstorm
Command: npx skills add https://github.com/leing2021/super-pi --skill 01-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you discover clear requirements when a request is ambiguous, underspecified, or introduces a new idea by running a structured multi-round dialogue that ends in an approved requirements artifact.

Core Features & Use Cases

  • Mode-based requirements discovery: Selects the right question set based on whether you are building a startup, running a side project, or adding a feature to an existing project.
  • Multi-round refinement with guardrails: Uses brainstorm_dialog to start, refine, and summarize while asking one question at a time and avoiding implementation details until later.
  • Premise Challenge + alternatives: Validates assumptions and generates 2-3 approaches (minimal viable + ideal architecture) to produce clear next steps.
  • Durable artifact output: Writes the resulting requirements document to docs/brainstorms/ and enforces an explicit user approval gate before handing off to 02-plan.

Quick Start

Ask for requirements discovery, for example: "I want to build a product, but I’m not sure what to build yet—run 01-brainstorm and capture a requirements artifact I can approve."

Frequently Asked Questions about 01-brainstorm

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

FAQPage Schema
How do I turn an ambiguous product idea into implementation-ready requirements?▼

To turn an ambiguous idea into implementation-ready requirements, use structured multi-round dialogue to clarify scope, validate premises, and generate alternative approaches before writing a durable spec artifact.

What is the best way to validate assumptions during requirements discovery?▼

Validating assumptions during requirements discovery involves challenging initial premises and generating 2-3 alternative approaches, comparing minimal viable architecture against ideal architecture to define clear next steps.

How do I write a spec for a new startup feature when I'm not sure what to build?▼

Writing a spec for an unsure startup feature requires mode-based requirements discovery, selecting targeted question sets to refine the idea through a guarded dialogue that avoids implementation details until the scope is clear.

Can I generate a requirements document for side projects without writing it manually?▼

Yes, you can generate a requirements document for side projects automatically. The process writes the finalized requirements artifact directly to a designated docs folder after an explicit user approval gate.

Does structured requirements discovery work for adding features to existing products?▼

Structured requirements discovery works for adding features to existing products by adapting its question sets to the context, ensuring new functionality aligns with current architecture through multi-stage refinement and premise validation.