skills.rest
friedbotstudio
friedbotstudioOFFICIAL
Explore all skills by this author →
GitHub

brainstorm

Capture ambiguous requests into structured requirement briefs before drafting.

5|Updated Apr 29, 2026
Search Tags:#tdd#requirements#spec#socratic#brainstorm#brief#intake
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill brainstorm-friedbotstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/friedbotstudio/baseline --skill brainstorm-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents teams from locking in a solution too early by turning an unclear request into a structured, requirement-first brief.

Core Features & Use Cases

  • Socratic requirement capture: Guides the requester through missing actor, trigger, current state, desired state, non-goals, and solution leakage.
  • Workflow gating: Runs as a step-zero helper for intake, spec, and tdd entry flows before any artifact drafting begins.
  • Discipline and persistence: Enforces probe-only dialogue, skips when configured or when a brief already exists, and writes the final brief for later stages to consume.

Quick Start

Ask the brainstorm skill to interview you about the request and produce a brief for the current slug before you begin intake, spec, or tdd work.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn vague project requests into clear requirement briefs?▼

A requirement brief captures missing actors, triggers, current states, desired states, and non-goals through Socratic probing. This prevents premature solution leakage and structures ambiguous project intake into a clear, requirement-first artifact.

What is the best way to prevent teams from locking in a solution too early during intake?▼

Preventing premature solution locking requires a step-zero discovery workflow with stage-based gap analysis and disciplined probing. This ensures all requirement gaps are resolved before any spec or TDD artifact drafting begins.

How does Socratic requirement capture work for software specs?▼

Socratic requirement capture works by guiding requesters through probe-only dialogue to identify missing actors, triggers, current states, desired states, and non-goals. This ensures discovery is complete before any spec or TDD drafting begins.

Can I skip the requirement interview if a brief already exists for my slug?▼

Yes, you can skip the requirement interview if a brief already exists for your current slug or if skipping is explicitly configured. The workflow handles skips automatically, allowing direct progression to downstream intake or spec stages.

When should I run requirement discovery before starting TDD entry workflows?▼

Run requirement discovery before TDD entry workflows whenever an initial request is ambiguous. This ensures a structured brief is persisted and open questions are tracked before committing to any test-driven development solution.

Related Skills

Explore More Product & Management Skills→
magnus919magnus919
40

product-discovery

Map stakeholders, conduct interviews, and distill requirements into formal specifications.

Community
Advanced
g2i-aig2i-ai
51

workflow

Route software delivery work through brief, spec, tdd, code, review, and draft-pr stages.

Official
Intermediate
olivomarcoolivomarco
66

cross-squad

Discover squad manifests and delegate tasks across repositories.

Community
Advanced
rafalwizenrafalwizen

maister:requirements-critic

Identify gaps and CRUD-disguised domain logic in software requirements.

Community
Intermediate