Skip to main
maude

Flow lifecycle

The 10 /flow:* slash commands, grouped by lifecycle. Flags select the lane, so one verb covers what used to be several commands.

Ten commands. The daily verbs stay one-word terse (plan, execute, validate, done); the rest wear a group prefix (bug-rca, bug-fix, record-ddr). Variants are flags, not separate commands: /flow:validate --security, /flow:plan --prd, /flow:execute --quick. Coming from the older 30-command surface? See Flow migration.

The canonical catalog: plugins/flow/CATEGORIES.md. Live command list: Claude Code's native /help.

Figure 1 · the /flow:* lifecycle
Setup
init
setup-prd
setup-context
.ai/ workspace + PRD
Plan
plan
status
plan-NNN.md
Execute
execute
quick
bug-fix
working code
Validate
validate
review-code
scenario
green gates
Done
done
record-ddr
record-retro
commit · PR · retro
Release
release
release-changelog
maintain-clean
tagged vX.Y.Z
.ai/ workspaceeverything the loop writes — nothing lives in a chat scroll
decisions/DDR-*.mdplans/archive/state/STATE.mdlogs/retro
11 daily verbs · one-word terse 19 grouped · group-verb prefix 30 commands · CATEGORIES.md

Setup. One-shot bootstrapping

Run once per project (or once per major restructure).

CommandWhat it does
/flow:initScaffold .ai/, auto-detect stack, populate workflows.config.json, defer to /init for CLAUDE.md.
/flow:init --contextPrime the agent with the codebase map + CLAUDE.md.
/flow:init --mapSnapshot architecture into .ai/context/ for cross-session reuse.
/flow:init --kgaiImport existing decisions into the kgai knowledge graph.
/flow:plan --prdDraft a PRD + auto-generate phase plans + execution README.

Daily. Every-cycle workflow

CommandWhat it does
/flow:plan "<feature>"Context-rich feature plan grounded in PRD + design system.
/flow:execute [plan-path]Execute an implementation plan task-by-task with an Edit-Verify loop. Slices are delegated to the flow:worker role agent.
/flow:execute --quickTrivial-change fast-path. Skip plan cycle, go edit, verify, commit.
/flow:run <plan>Drive a plan to completion as a goal. Opt-in capped Stop hook; --pause, --resume, --status, --stop.
/flow:validateFull pipeline: static + tests + build + scenario + a11y + design.
/flow:done/validate gate, DDR sweep, commit, push, PR, execution report, retro, archive.
/flow:releaseWalk the project's release runbook step-by-step with explicit confirmation. --changelog authors the changelog entry.

Validate. One command, several lanes

/flow:validate runs the pipeline; flags run a single lane.

CommandWhat it does
/flow:validate --fastLight scoped per-file check (what the Edit-Verify loop runs).
/flow:validate --securitySecurity review (security-auditor + ethical-hacker subagents), aggregated report, gates on severityFloor.
/flow:validate --a11yAccessibility audit (WCAG 2.1 AA).
/flow:validate --visualVisual regression check with screenshots.
/flow:validate --reviewPre-commit self-review of uncommitted changes.
/flow:validate --scenarioCross-platform UI scenario with screenshot evidence.

Bug. Incident workflow

CommandWhat it does
/flow:bug-rca <issue-id>Analyze and document root cause for a GitHub issue.
/flow:bug-fix <issue-id>Implement the fix from the RCA document.

Record. Knowledge capture

CommandWhat it does
/flow:record-ddr "<title>"Record a Design Decision Record.

The execution report and the retrospective are now steps of /flow:done.

Role agents

/flow:execute and /flow:run hand bounded work to three role agents: flow:worker (implements one self-contained task slice), flow:spike (answers one open question with a throwaway prototype) and flow:scout (read-only inventory). The flow:context-budget skill holds the rules for what each may read and return.

MDCC-DGM/TRCommandTree
/flow:
10 commands · grouped in CATEGORIES.md
Flow commands by group — each leaf links to its reference page

On this page