# Capture Requirements Before Implementation

Teams lose time when vague requests become rushed implementation. This skill structures early brainstorming, compares options, and records decisions for later alignment.

## Install

```bash
npx skillstore add dimon94/flow-brainstorming
```

## Metadata

- Status: approved
- Slug: dimon94-flow-brainstorming
- Skillstore revision: r1
- Version status: missing
- Tree hash: 015c8339f7d8c7e45825065c16cdb2d6948ad471dc9e2186f569279e4b355653
- Author: Dimon94
- GitHub username: Dimon94
- License: MIT
- Repository: https://github.com/Dimon94/cc-devflow/tree/main/.claude/skills/flow-brainstorming
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dimon94-flow-brainstorming
- Manifest: https://skillstore.pages.dev/api/skills/dimon94-flow-brainstorming/manifest

## Capabilities

- Guides one-question-at-a-time requirement clarification.
- Prompts the assistant to inspect project state, documents, and recent commits.
- Presents two or three implementation approaches with tradeoffs.
- Requires incremental validation of architecture, components, data flow, errors, and tests.
- Defines required sections for a BRAINSTORM.md decision record.
- Adds alignment checks for later flow stages.

## Use Cases

- Clarify a New Feature: Turn an initial product idea into purpose, constraints, success criteria, and candidate approaches.
- Compare Technical Paths: Review multiple implementation strategies before choosing one and documenting the decision.
- Prevent Rushed Changes: Slow down small fixes enough to capture the original need and avoid hidden assumptions.

## Prompt Templates

### Start Requirement Brainstorm

```
Use flow-brainstorming for this request: {request}. Ask one clarifying question at a time before proposing a design.
```

### Compare Approaches

```
Use flow-brainstorming to explore two or three approaches for {feature}. Include tradeoffs and recommend one option.
```

### Validate A Design

```
Use flow-brainstorming to present the proposed design for {request} in short sections. Ask for confirmation after each section.
```

### Create Alignment Record

```
Use flow-brainstorming for REQ {id}: {title}. Capture original wording, success criteria, constraints, alternatives, decision, and alignment checks.
```

## Limitations

- Does not implement code or run tests by itself.
- Assumes the surrounding DevFlow process and requirement IDs exist.
- Relies on the assistant and user to keep BRAINSTORM.md accurate.
- Uses prose instructions only; it does not provide executable automation.

## Best Practices

- Ask one question per message until purpose, constraints, and success criteria are clear.
- Record the user's original wording before summarizing or refining the request.
- Recheck BRAINSTORM.md before later implementation phases.

## Anti Patterns

- Skipping brainstorming because the request sounds small.
- Choosing one design before comparing alternatives.
- Writing a decision record without user confirmation.

## Security Audit

- Audited at: 2026-07-06T12:47:02.959\+00:00
- Summary: The command-execution findings are false positives caused by Markdown code fences in SKILL.md examples. The entropy findings are false positives caused by readable Chinese prose and plain Markdown content; no evidence found of prompt injection, obfuscation, data exfiltration, or malicious intent.

## Stats

- Views: 199
- Downloads: 26
- Favorites: 0
- Popularity score: 0