prd-brainstorm

Convert vague product ideas and PRD fragments into structured FR/NFR requirement documents.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill prd-brainstorm-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-brainstorm
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/prd-brainstorm
Command: npx skills add https://github.com/ab300819/keel-workflow --skill prd-brainstorm-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a one-line idea or a messy PRD fragment into traceable, prioritized requirements is slow and error-prone. This Skill guides structured requirement exploration so nothing important is missed and every requirement gets a stable FR/NFR identifier. ## Core Features & Use Cases - Full Brainstorm Mode: Walks a vague idea through 5W1H positioning, user role identification, journey mapping, and MoSCoW prioritization to produce structured requirements. - Chunk Clarification Mode: Clarifies PRD segments split by prd-parser using a 6-item depth rubric, with fast-confirm or deep-exploration paths capped at 3 questioning rounds. - FR/NFR Final Classification & Numbering: Re-judges parser classifications, assigns sequential FR-XX/NFR-XX IDs, and writes requirement files with realign metadata to docs/prd/requirements/. - Use Case: You have a rough idea for a user authentication feature. Run the brainstorm flow to clarify roles, scenarios, and acceptance intent, then output a ready FR document consumable by the keel requirements pipeline. ## Quick Start Ask the assistant to brainstorm your one-sentence product idea into structured requirements using the prd-brainstorm skill.

Frequently Asked Questions about prd-brainstorm

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

FAQPage Schema
How do I turn a vague product idea into structured requirements?

Run the full brainstorm mode, which guides the idea through 5W1H positioning, user role identification, journey mapping, and MoSCoW prioritization. Each confirmed requirement is written as an FR-XX or NFR-XX file under docs/prd/requirements/.

How does PRD chunk clarification work with prd-parser?

After prd-parser splits a large PRD into chunk files, this skill reads each chunk, scores it against a 6-item depth rubric, and either fast-confirms it or asks up to 3 rounds of clarifying questions before outputting the structured requirement.

What is the difference between FR and NFR classification?

FR covers user operations, interaction flows, business logic, and data processing, while NFR covers performance, security, availability, compatibility, and maintainability. The skill re-judges the parser's initial classification and records any change via a reclassified_to field in the chunk YAML header.

When should I use requirements instead of prd-brainstorm?

Use requirements directly when your needs are already clear and structured. prd-brainstorm is for fuzzy ideas or PRD fragments that still need exploration, clarification, and MoSCoW prioritization before entering the keel pipeline.

What are the limitations of the chunk clarification mode?

Clarification is capped at 3 rounds of user questions per chunk; unresolved items are forced into output as open questions rather than assumed answers. The skill also never modifies original chunk content beyond adding a reclassification field to the YAML header.