AIDoc Flow plugin for Claude Code
Pre-release v0.18.0 — breaking changes possible between minor versions. Your bug reports help.
The plugin drives Claude Code through the AIDoc Flow eight-layer spec-driven loop — BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN — with multi-persona review crews and a deterministic structural-gate floor on every layer. Claude itself does the generation, validation, and scoring; there's no MCP backend and nothing to run separately.
Install
From a Claude Code session:
/plugin marketplace add vladm3105/aidoc-flow-framework
/plugin install aidoc-flow@aidoc-flow-framework The plugin is self-contained — it vendors the framework spec it needs, so it installs and runs from a marketplace with no external checkout, no MCP server, no extra setup.
Quickstart
The five commands to go from empty repo to a green BRD:
/aidoc-flow:doc-flow # "which skill do I need?" — start here
/aidoc-flow:project-init # scaffold the docs/ layer tree
/aidoc-flow:doc-brd-autopilot # draft the first layer (BRD) end-to-end
/aidoc-flow:doc-brd-audit # score it against the layer's quality gate
/aidoc-flow:doc-validator # validate cross-doc refs & traceability
Work down the layers (doc-prd, doc-ears, …
doc-iplan), running each layer's -audit
before promoting to the next. doc-flow is the
orchestrator: describe your goal and it routes you to the right skill.
What's inside
| Component | Count | What it is |
|---|---|---|
| Skills — layer families | 32 |
The 8 SDD layers (doc-brd, doc-prd,
doc-ears, doc-bdd, doc-adr,
doc-spec, doc-tdd, doc-iplan)
— each in 4 variants: base, -autopilot,
-audit, -fixer.
|
| Skills — change governance | 4 |
The CHG overlay — doc-chg +
-autopilot + -audit + -fixer
(governs edits to existing artifacts; not a layer).
|
| Skills — utilities | 14 | doc-flow, doc-naming, doc-ref,
doc-validator, review-team,
project-init, project-adopt,
project-profile, knowledge-extractor,
gate-check, charts-flow,
adr-roadmap, quality-advisor,
security-audit.
|
| Review agents | 11 |
AI Team specialists — requirements-analyst,
pm-orchestrator, solutions-architect,
test-architect, software-engineer,
devops-release-engineer, code-reviewer,
security-engineer, traceability-auditor,
plus review-team lenses chaos-engineer and
synthesizer.
|
| Commands | 1 | /aidoc-flow:save-plan — capture the current conversation plan to a timestamped file. |
| Hooks | 1 | PostToolUse advisory nudge — when you write an
SDD doc, it surfaces deterministic structural findings inline.
Never blocks the edit.
|
| Total skills | 52 | 50 active + 2 deprecated stubs scheduled for removal in v0.7.0. |
Full skill catalog
Per-layer skills (32)
Each of the 8 SDD layers ships in 4 variants — the same shape every time:
doc-<layer>— author the layer's artifact (template-driven)doc-<layer>-autopilot— draft + audit + fix in one cascadedoc-<layer>-audit— score against the layer's quality gate (default 90)doc-<layer>-fixer— apply remediation findings
Where <layer> is one of brd,
prd, ears, bdd, adr,
spec, tdd, iplan — e.g.
doc-brd-autopilot, doc-iplan-audit.
CHG governance overlay (4)
Same 4-variant shape, but governs edits to existing artifacts rather than authoring a new layer:
doc-chg·doc-chg-autopilot·doc-chg-audit·doc-chg-fixer
Utility skills (14 active + 2 deprecated stubs)
| Skill | What it does |
|---|---|
doc-flow | Orchestrator — describe your goal, it routes to the right skill. Start here. |
doc-naming | Naming-convention enforcement across the spec chain. |
doc-ref | Cross-document reference resolver (used by validator + auditors). |
doc-validator | Validate cross-doc references, trace tags, and traceability coverage. |
review-team | Multi-persona review-crew dispatcher — fans out lens subagents in parallel. |
project-init | Scaffold the docs/ layer tree for a new project. |
project-adopt | Bring an existing codebase into the SDD flow (back-fill the spec chain). |
project-profile | Print the current project's .aidoc/profile.yaml knobs. |
knowledge-extractor | Pull entities, decisions, and glossary terms out of an artifact into the corpus. |
gate-check | Show the gate status (pass / fail / score) across every layer. |
charts-flow | Generate Mermaid charts from the spec chain. |
adr-roadmap | Produce a roadmap from the ADR set. |
quality-advisor | Advisory quality findings across the corpus. |
security-audit | Security-lens sweep across the corpus. |
doc-review | Deprecated stub — aliased to review-team; removed in v0.7.0. |
trace-check | Deprecated stub — superseded by doc-validator; removed in v0.7.0. |
Review crews — the differentiator
Every layer has its own weighted review crew. In
team mode (default at gates), the layer's audit skill
fans out one Claude Code Task subagent per lens, in
parallel, each writing its persona-output record to a slot on a
per-artifact blackboard. The synthesizer agent then
reduces the slots deterministically and produces a single readiness
score against the gate floor (default 90).
| Layer | Author lens | Review crew (lens → weight, sums to 100) |
|---|---|---|
| BRD | business_analyst | architect 30 · business_analyst 30 · auditor 20 · chaos_engineer 12 · security_engineer 8 |
| PRD | product_owner | product_owner 30 · architect 25 · tech_lead 20 · auditor 10 · chaos_engineer 8 · security_engineer 7 |
| EARS | requirements_specialist | requirements_specialist 35 · tech_lead 25 · qa_lead 20 · chaos_engineer 12 · security_engineer 8 |
| BDD | qa_lead | qa_lead 35 · tech_lead 25 · chaos_engineer 14 · auditor 10 · operator 10 · security_engineer 6 |
| ADR | architect | architect 35 · tech_lead 25 · security_engineer 12 · auditor 10 · operator 10 · chaos_engineer 8 |
| SPEC | architect | architect 30 · tech_lead 30 · integration_lead 20 · chaos_engineer 10 · security_engineer 10 |
| TDD | qa_lead | qa_lead 35 · tech_lead 25 · chaos_engineer 10 · security_engineer 10 · operator 10 · auditor 10 |
| IPLAN | tech_lead | tech_lead 30 · architect 25 · operator 15 · integration_lead 12 · auditor 10 · chaos_engineer 8 |
Crews + weights are declared in
framework/governance/REVIEW_CREWS.yaml; the model
contract is in
framework/governance/REVIEW_TEAM.md. BRD is currently
fully wired for team mode (BRD-RT-001); the other layers
fall back to single_pass while per-layer wiring lands
(PRD-RT, EARS-RT, … coming).
Per-layer playbooks (51)
Each lens, on each layer, carries a playbook: layer-specific finding categories the lens looks for, with worked examples. The audit skill injects the relevant playbook into each lens subagent's brief, so reviews stay grounded in layer-shaped checks rather than generic prose. 45 of 45 lens-specific finding categories covered across the SDD layers; 6 additional playbooks for the CHG overlay.
| Layer | Playbooks (one per lens) |
|---|---|
| BRD (5) | architect · auditor · business_analyst · chaos_engineer · security_engineer |
| PRD (6) | architect · auditor · chaos_engineer · product_owner · security_engineer · tech_lead |
| EARS (5) | chaos_engineer · qa_lead · requirements_specialist · security_engineer · tech_lead |
| BDD (6) | auditor · chaos_engineer · operator · qa_lead · security_engineer · tech_lead |
| ADR (6) | architect · auditor · chaos_engineer · operator · security_engineer · tech_lead |
| SPEC (5) | architect · chaos_engineer · integration_lead · security_engineer · tech_lead |
| TDD (6) | auditor · chaos_engineer · operator · qa_lead · security_engineer · tech_lead |
| IPLAN (6) | architect · auditor · chaos_engineer · integration_lead · operator · tech_lead |
| CHG (6) | architect · auditor · chaos_engineer · integration_lead · operator · security_engineer |
Playbooks live under framework/playbooks/<NN>_<LAYER>/<lens>.md.
Each ships a stable schema (finding categories, severity, example
detect+fix pairs) consumed by the per-layer audit skills.
Project overrides — tune the gate
Drop a .aidoc/profile.yaml in your project to override
review behaviour:
-
review_mode: team | single_pass—teamfans out per-lens subagents;single_passruns one model context applying every lens. Defaults toteamat gates. -
audit_threshold: <int>— raise the gate score floor (raise-only; can't go below the framework default of 90). -
section_toggles— toggle optional template sections (e.g. BRD §2 Executive Summary). -
active_layers— restrict the cascade to a subset of the 8 layers.
The closed adaptation surface is defined in
framework/governance/ADAPTATION_SURFACE.yaml —
these are the only knobs a project may turn.
Platform info
| Engine | Native Claude Code (skills / agents / commands — no MCP) |
| Plugin version | 0.18.0 (tag namespace claude-code-plugin/v*) |
| Conforms to | framework spec 0.21.1 (declared in FRAMEWORK_SPEC_VERSION) |
| License | MIT |
| Repository | vladm3105/aidoc-flow-framework |
Status — pre-release, in flight
The framework spec is at v0.21.1; the plugin at
v0.18.0. We use it on ourselves daily. The install
command is stable; the SKILL surface is still settling. Expect
breaking changes between minor versions until v1.0.
Found a bug? Surprised by a behaviour? Have a half-formed idea? Drop
it in GitHub
Issues — the messier, the better. This is the dev site; the
polished release notes live at aidoc-flow.ai when it
ships.