From code-flow
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Discovers requirements and acceptance criteria through collaborative dialogue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-flow:brainstormingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help turn ideas into clear requirements and acceptance criteria through natural collaborative dialogue. The conversation is the main event — ask questions to find the edges of what the user wants before writing anything down.
Help turn ideas into clear requirements and acceptance criteria through natural collaborative dialogue. The conversation is the main event — ask questions to find the edges of what the user wants before writing anything down.
Get oriented:
Discover requirements through questions:
AskUserQuestion tool when available — it supports multiple choice options, which are faster for the user to answer and keep the conversation focusedExplore approaches (briefly):
Present the spec:
Write the validated spec to docs/specs/YYYY-MM-DD-<topic>.md with this structure:
# [Topic]
**Goal:** [One sentence]
**Constraints:**
- [Constraint 1]
- [Constraint 2]
**Out of scope:**
- [Thing 1]
**Acceptance Criteria:**
1. [Criterion 1]
2. [Criterion 2]
3. [Criterion 3]
Next steps (if continuing):
npx claudepluginhub aeriondyseti/aeriondyseti-plugins --plugin code-flowCollaboratively explores feature requirements and options through dialogue, producing a right-sized requirements document for implementation planning. Use for vague ideas, brainstorming, or scoping ambitious requests.
Explores feature ideas and requirements via collaborative dialogue, then generates a right-sized requirements document for planning. Use for vague requests, brainstorming, or scoping ambiguous problems.
Guides pre-implementation design exploration by asking one question at a time to produce a written spec before any code is written.