doc-prd

The AI Dev Flow Framework is a comprehensive template system for implementing AI-Driven Specification-Driven Development (SDD). It provides structured workflows, document templates, and traceability mechanisms to transform business requirements into production-ready code through a systematic, traceable approach optimized for AI-assisted development.

> MVP Note: When using the MVP track, all artifacts are single, flat files. Do not use document splitting or DOCUMENT_SPLITTING_RULES.md.

PRIMARY GOAL: Fastest Transition from Business Idea to Production MVP

AI Dev Flow eliminates manual bottlenecks through intelligent automation and strategic human oversight.

Automation Capabilities:

• Quality-Gated Automation: Replace mandatory checkpoints with AI-scored quality validation

- Auto-approve if quality score ≥ threshold (90-95%)

- Human review only if score fails

- Result: Up to 93% automation (12 of 13 production layers)

• AI Code Generation: YAML specs → Production-ready code
• Auto-Fix Testing: 3 retry attempts reduce manual debugging
• Strategic Checkpoints: Only 5 critical decisions need human approval if quality score < threshold (90%)
• Continuous Pipeline: Automated validation, security scanning, deployment builds

Human-in-the-Loop Checkpoints (Quality Gates):

| Layer | Checkpoint | Why Human Review? |

|-------|------------|------------------|

| L1 (BRD) | Business owner approves | Strategic business alignment |

| L2 (PRD) | Product manager approves | Product vision validation |

| L5 (ADR) | Architect approves | Technical architecture decisions |

| L11 (Code) | Developer reviews | Code quality and security |

| L13 (Deployment) | Ops approves | Production release gating |

Automated Layers (No human intervention required):

• L3 (EARS), L4 (BDD), L6 (SYS), L7 (REQ), L8 (CTR), L9 (SPEC), L10 (TASKS), L12 (Tests)

Result: Dramatically reduced manual effort while maintaining quality through strategic oversight.

AI Dev Flow supports continuous product evolution through iterative MVP cycles:

The Delivery Loop:

```

┌─────────────────────────────────────────────────┐

│ MVP v1.0 → Defect Fixes → Production Release │

│ ↓ │

│ MVP v2.0 (Add Features) ← Market Feedback │

│ ↓ │

│ Defect Fixes → Production │

│ ↓ │

│ MVP v3.0 (Add Features) ← ... │

└─────────────────────────────────────────────────┘

```

Key Benefits:

• Rapid Iteration: Complete L1-L13 pipeline with 90% automation
• Incremental Features: Add features as new MVPs, preserve working product
• Production Focus: Every MVP targets production deployment
• Cumulative Traceability: Each MVP inherits and extends previous version's artifacts

How Automation Enables the Loop:

| Stage | Automation Support |

|-------|-------------------|

| Build MVP v1.0 | Full L1-L13 automation (90% automated) |

| Fix Defects | Auto-retry testing (3x), auto-fix capabilities |

| Deploy to Production | Automated build, validation, security scans |

| Add Features (MVP v2.0) | Reuse or create new BRD/PRD/ADR, auto-generate new REQ→CODE |

| Iterate | Cumulative tags enable impact analysis |

MVP Evolution Example:

• MVP 1.0: User authentication → Production
• Defect Fixes: Password reset bugs → Production
• **MVP 2