do-brainstorm

Transforms vague ideas into structured requirement.md files through Socratic dialogue.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/khoavu882/do-flow --skill do-brainstorm-khoavu882
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-brainstorm
Source: https://github.com/khoavu882/do-flow/tree/main/core/shared/skills/do-brainstorm
Command: npx skills add https://github.com/khoavu882/do-flow --skill do-brainstorm-khoavu882

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New feature ideas often start vague, leading teams to jump into design or coding before requirements are understood. This Skill runs a structured discovery phase that turns an ambiguous idea into a concrete, persisted requirement document before any design or planning begins. ## Core Features & Use Cases - Socratic Requirements Discovery: Runs iterative clarification rounds with batched questions, a "Decide for me" defer option, and per-round dialogue logs saved to the feature directory. - Branch-Coupled Artifact Generation: Resolves the active feature via the DoFlow runtime, creates the feature branch and directory when needed, and writes a WHAT/WHY-only requirement.md with user stories, FRs, NFRs, and acceptance criteria. - Workflow Orchestration & Evidence: Validates the proposed task class, batches evidence and claims, records the stage handoff, and resolves the clarification gate as Phase 1 of the doflow chain. - Use Case: You say "I have an idea for a notification system" — the Skill interviews you about users, outcomes, and scope, then produces agent-docs/doflow/<slug>/intention/requirement.md ready for /do-design. ## Quick Start Ask the AI to run /do-brainstorm with your feature idea, for example: brainstorm what we need for a user notification preferences feature.

Frequently Asked Questions about do-brainstorm

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

FAQPage Schema
How do I turn a vague feature idea into requirements with AI?▼

Invoke /do-brainstorm with your idea and it runs Socratic dialogue rounds to clarify the problem, users, and outcomes. It then writes a requirement.md with user stories, functional requirements, NFRs, and acceptance criteria into the feature directory.

What is the doflow chain and where does brainstorming fit?▼

The doflow chain is do-brainstorm, do-design, do-plan, do-execute-plan, do-test, do-code-review. do-brainstorm is Phase 1, the discovery stage that produces requirement.md, which later stages consume for architecture and planning.

Does do-brainstorm make technical or architecture decisions?▼

No. It deliberately excludes implementation and stack choices, capturing only WHAT and WHY: user problems, personas, business outcomes, and acceptance criteria. Architecture decisions are deferred to /do-design to avoid premature technical bias.

What happens if I answer 'Decide for me' during discovery questions?▼

The question resolves through a recorded assumption rather than re-prompting. The assumption is written into the requirement template's Assumptions section with a one-line rationale, so the artifact stays complete without forcing an answer.

Why does do-brainstorm fail with 'no runtime found'?▼

The Skill requires the DoFlow runtime at .doflow/scripts/doflow/bin/doflow-run in the project or home directory. If missing, run npx @khoavu882/doflow install, then retry; the error message lists every path searched.

When should I not use do-brainstorm?▼

Skip it when requirements are already clear or the accepted workflow has no discovery stage; the Skill itself hands off to the first stage the workflow names. It also stops if the runtime rejects the proposed task class.