Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By vladm3105
Enforces a complete Specification-Driven Development workflow across 8 documentation layers (BRD → IPLAN), with agents and skills to author, audit, fix, and trace artifacts, plus gates for code implementation, security review, and release governance.
npx claudepluginhub vladm3105/aidoc-flow-framework --plugin aidoc-flow**Specialist Claude Code subagents for the AI Doc Flow Framework's Specification-Driven Development (SDD) flow.**
Use this agent to review code changes and pull requests for quality, standards compliance, spec/test conformance, and acceptance-criteria verification. A READ-ONLY quality gate: it reports findings and a verdict, it never edits code itself. A downstream-heavy role built out in depth, since the success-story data shows review/test compression drives the largest gains.
Use this agent for CI/CD, build/test pipelines, deployment governance, and release readiness across the execution lane. Owns the path from merged code to deployed, observed, and verified release, including staging/prod gates and the post-deploy evidence loop.
Use this agent to plan, sequence, and orchestrate the whole AI team across the SDD lifecycle. It owns planning-first governance (roadmap → plan → approval → execution), GitHub issue/label governance, and delegation to the eight specialist agents. It drives the document lifecycle through the plugin's native SDD skills and is the PM seat the team plugs into.
Use this agent when decomposing, analyzing, and validating requirements across the SDD workflow. Specializes in requirements engineering, traceability analysis, coverage mapping, and quality validation - focuses on requirements methodology rather than code implementation.
Generate a phased implementation roadmap from a set of Architecture Decision Records, with dependencies, timeline, risk, and testing strategy. Use when coordinating delivery of multiple ADRs.
Create and manage Mermaid architecture diagrams as separate, traceable files linked to their parent SDD documents. Use when adding or migrating diagrams for BRD, PRD, ADR, SPEC, or IPLAN documents.
Scan a project's SDD artifacts and build a context model (inventory, traceability graph, workflow position, upstream candidates) to inform new document creation. Use before authoring an artifact in an existing project.
Audit an ADR - run declarative structural checks plus content review and produce a combined report for doc-adr-fixer. Use for ADR quality gating before SPEC.
Generate ADRs end-to-end from an upstream artifact (BRD/PRD/EARS/BDD), a prompt, or an IPLAN - detect input, scope the decision, generate, validate, and run the audit/fix cycle. Use to create or batch-create ADRs.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Comprehensive AI-assisted development workflow system with specialized agents, orchestrated commands, and file-based state management
Documentation agents — technical writer, documentation architect
Spec-driven development methodology for Claude Code. Provides skills for requirements engineering (EARS format), design documentation, task breakdown, AI prompting strategies, quality assurance, and troubleshooting.
Document Driven Development — a structured workflow for AI-assisted software development with TDD, specs, and cross-review
Autonomous spec-driven development workflow with multi-agent collaboration, specification management, and task orchestration
Spec-driven development methodology for full-stack teams
A specification-driven document-flow framework for AI-assisted software development, delivered as one engine-agnostic specification with two independent platforms.
framework/ Engine-agnostic specification (the shared contract)
platforms/
hermes/ Platform A — Hermes AI (MCP-server engine)
claude-code-plugin/ Platform B — Claude Code plugin (native engine)
tests/
conformance/ Shared suite both platforms must pass
The framework/ spec defines the 8-layer SDD flow
(BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code), schemas, templates,
and governance. Each platform is an independent implementation of that spec —
they share the specification and nothing else, and both pass the same
conformance suite at tests/conformance/.
| Platform | Engine | Release |
|---|---|---|
| Hermes AI | MCP server | hermes/v0.1.0 (platforms/hermes/) |
| Claude Code plugin | Native Claude Code (skills / agents / commands) | claude-code-plugin/v0.2.0 (platforms/claude-code-plugin/) |
See docs/PARITY.md for the capability comparison and a
"which platform should I use?" guide.
This repo doubles as a plugin marketplace (.claude-plugin/marketplace.json).
From Claude Code:
/plugin marketplace add vladm3105/aidoc-flow-framework
/plugin install aidoc-flow@aidoc-flow-framework
ROADMAP.md — phased delivery plan (Phase 0 → cutover v1.0.0).CHANGELOG.md — project-level changelog.docs/REPO_STRUCTURE.md — repository layout (as-built).docs/PROJECT.md — versioning, branching, milestones, conformance, change management.docs/TAGGING.md — git-tag policy (release + bookmark tags).docs/PARITY.md — Hermes ↔ plugin capability comparison.framework/README.md — the engine-agnostic SDD specification.This project was migrated from the pre-migration ucx_framework (v0.20.4)
into the multi-platform structure above. The pristine pre-migration project
is preserved on the protected, read-only branch
legacy-ucx-v3.2-read-only (git checkout legacy-ucx-v3.2-read-only).
The full migration record — per-task plans, audits, verify records, and the
decision log — lives under plans/.