doc-prd-autopilot

Purpose

Automated Product Requirements Document (PRD) generation pipeline that processes one or more BRD documents and generates their corresponding PRDs with dependency awareness, readiness validation, and parallel execution support.

Layer: 2 (PRD Generation)

Upstream: BRD (Layer 1)

Downstream: EARS (Layer 3), BDD (Layer 4), ADR (Layer 5)

Input Contract (IPLAN-004 Standard)

Supported modes:
--ref <path>
--prompt "<text>"
--iplan <path|IPLAN-NNN>
Precedence: --iplan > --ref > --prompt
IPLAN resolution order:
Use explicit file path when it exists
Resolve work_plans/IPLAN-NNN*.md
Resolve governance/plans/IPLAN-NNN*.md
If multiple matches exist, fail with disambiguation request
Merge conflict rule:
Objective/scope conflicts between primary and supplemental sources are blocking and require user clarification.

Input Contract (IPLAN-004 Standard)

Supported modes:
--ref <path>
--prompt "<text>"
--iplan <path|IPLAN-NNN>
Precedence: --iplan > --ref > --prompt
IPLAN resolution order:
Use explicit file path when it exists
Resolve work_plans/IPLAN-NNN*.md
Resolve governance/plans/IPLAN-NNN*.md
If multiple matches exist, fail with disambiguation request
Merge conflict rule:
Objective/scope conflicts between primary and supplemental sources are blocking and require user clarification.

Skill Dependencies

This autopilot orchestrates the following skills:

Skill Purpose Phase

doc-naming

Element ID format, threshold tags, legacy pattern detection All Phases

doc-brd-audit

Validate BRD PRD-Ready score (unified audit) Phase 2: BRD Readiness

doc-prd

PRD creation rules, template, section structure Phase 3: PRD Generation

quality-advisor

Real-time quality feedback during PRD generation Phase 3: PRD Generation

doc-prd-validator

Validate PRD structure, content, EARS-Ready score Phase 4: PRD Validation

doc-prd-reviewer

Content review, link validation, quality scoring Phase 5: Review

doc-prd-audit

Unified validator+reviewer audit report generation Phase 5: Review

doc-prd-fixer

Apply fixes from review report, create missing files Phase 5: Fix

Delegation Principle: The autopilot orchestrates workflow but delegates:

PRD structure/content rules → doc-prd skill
Real-time quality feedback → quality-advisor skill
PRD validation logic → doc-prd-validator skill
BRD validation logic → doc-brd-audit skill (unified BRD quality gate)
Content review and scoring → doc-prd-reviewer skill
Issue resolution and fixes → doc-prd-fixer skill

Document Type Contract (MANDATORY)

When generating PRD document instances, the autopilot MUST:

Read instance_document_type from template:

Source: ai_dev_ssd_flow/02_PRD/PRD-MVP-TEMPLATE.yaml
Field: metadata.instance_document_type: "prd-document"

Set document_type in generated document frontmatter:

custom_fields: document_type: prd-document # NOT "template" artifact_type: PRD layer: 2

Validation: Generated documents MUST have document_type: prd-document

Templates have document_type: template
Instances have document_type: prd-document
Schema validates both values

Error Handling: If instance_document_type is missing from template, default to prd-document .

Smart Document Detection

The autopilot automatically determines the action based on the input document type.

Input Type Recognition

Input Detected As Action

PRD-NN

Self type Review existing PRD document

BRD-NN

Upstream type Generate if missing, review if exists

Detection Algorithm

Parse input: Extract TYPE and NN from "{TYPE}-{NN}"
Determine action:
- IF TYPE == "PRD": Review Mode
- ELSE IF TYPE == "BRD": Generate/Find Mode
- ELSE: Error (invalid type for this autopilot)
For Generate/Find Mode:
- Check: Does PRD-{NN} exist in docs/02_PRD/?
- IF exists: Switch to Review Mode for PRD-{NN}
- ELSE: Proceed with Generation from BRD-{NN}

File Existence Check

Check for nested folder structure (mandatory)

ls docs/02_PRD/PRD-{NN}_*/

Examples

Review mode (same type - PRD input)

/doc-prd-autopilot PRD-01 # Reviews existing PRD-01

Generate/Find mode (upstream type - BRD input)

/doc-prd-autopilot BRD-01 # Generates PRD-01 if missing, or reviews existing PRD-01

Multiple inputs

/doc-prd-autopilot BRD-01,BRD-02 # Generates/reviews PRD-01 and PRD-02 /doc-prd-autopilot PRD-01,PRD-02 # Reviews PRD-01 and PRD-02

Action Determination Output

Input: BRD-01 ├── Detected Type: BRD (upstream) ├── Expected PRD: PRD-01 ├── PRD Exists: Yes → docs/02_PRD/PRD-01_f1_iam/ └── Action: REVIEW MODE - Running doc-prd-audit on PRD-01

Input: BRD-05 ├── Detected Type: BRD (upstream) ├── Expected PRD: PRD-05 ├── PRD Exists: No └── Action: GENERATE MODE - Creating PRD-05 from BRD-05

Input: PRD-03 ├── Detected Type: PRD (self) └── Action: REVIEW MODE - Running doc-prd-audit on PRD-03

Review Mode Mandatory Steps (CRITICAL)

When entering REVIEW MODE (either via PRD-NN input or BRD-NN with existing PRD), the autopilot MUST:

Run doc-prd-audit (not just read existing reports)
Create/Update .drift_cache.json in the PRD folder
Generate fresh audit report (PRD-NN.A_audit_report_vNNN.md )

NEVER skip audit execution by only reading existing reports. Each autopilot invocation must produce fresh validation results and update drift tracking.

When to Use This Skill

Use doc-prd-autopilot when:

You have one or more completed BRD documents ready for PRD generation
You want automated dependency analysis to determine optimal PRD creation order
You need PRD-Ready score validation before generation
You want automatic EARS-Ready score validation after PRD creation
You need parallel PRD generation for independent BRDs

Do NOT use when:

Creating a single PRD with extensive manual customization (use doc-prd instead)
BRDs are incomplete or in Draft status
You need fine-grained control over each PRD section

8-Step Autopilot Workflow

Overview Diagram

flowchart TD subgraph Phase1["Phase 1: Dependency Analysis"] A[Input: BRD List] --> B[Analyze Dependencies] B --> C[Build Dependency Graph] C --> D[Topological Sort] D --> E[Define Creation Order] end

subgraph Phase2["Phase 2: BRD Readiness"]
    E --> F{Next BRD}
    F --> G[Check PRD-Ready Score]
    G --> H{Score >= 90?}
    H -->|No| I[Auto-Fix Issues]
    I --> J[Re-validate]
    J --> H
    H -->|Yes| K[Mark BRD Ready]
end

subgraph Phase3["Phase 3: PRD Generation"]
    K --> L[Load BRD Content]
    L --> M[Apply PRD Template]
    M --> N[Generate PRD Sections]
    N --> N2[quality-advisor: Real-time Feedback]
    N2 --> O[Add Traceability Tags]
    O --> P[Write PRD Files]
end

subgraph Phase4["Phase 4: PRD Validation"]
    P --> Q[Check EARS-Ready Score]
    Q --> R{Score >= 90?}
    R -->|No| S[Auto-Fix PRD Issues]
    S --> T[Re-validate PRD]
    T --> R
    R -->|Yes| U[Validation Passed]
end

subgraph Phase5["Phase 5: Final Review"]
    U --> U1[Check Link Integrity]
    U1 --> U2[Verify Threshold Consistency]
    U2 --> U3[Validate BRD Alignment]
    U3 --> U4[Check Placeholder Text]
    U4 --> U5{Review Passed?}
    U5 -->|No| U6[Flag Issues]
    U6 --> U7[Auto-Fix or Manual]
    U7 --> U5
    U5 -->|Yes| U8[Mark PRD Complete]
end

subgraph Phase6["Phase 6: Parallel/Continue"]
    U8 --> V{More BRDs?}
    V -->|Yes| W{Independent?}
    W -->|Yes| X[Parallel Generation]
    W -->|No| F
    X --> F
    V -->|No| Y[Generate Summary Report]
end

Y --> Z[Complete]

Step 1: Input Document List

Command Format:

/doc-prd-autopilot <DOCUMENT_LIST>

Input Patterns (Smart Detection):

Pattern Type Action

BRD-NN

Upstream Generate PRD if missing, review if exists

PRD-NN

Self Review existing PRD document

BRD-NN,BRD-MM

Multiple upstream Batch generate/review

PRD-NN,PRD-MM

Multiple self Batch review

all

All upstream Process all BRDs

Input Options:

Single BRD (generate/find): BRD-01 or docs/01_BRD/BRD-01_f1_iam/
Single PRD (review): PRD-01 or docs/02_PRD/PRD-01_f1_iam/
Multiple BRDs: BRD-01,BRD-02,BRD-03 (comma-separated)
Multiple PRDs: PRD-01,PRD-02,PRD-03 (comma-separated)
All BRDs: all or * (scan entire docs/01_BRD/ directory)
Pattern Match: BRD-0* or PRD-0* (glob patterns)

Example Invocations:

Generate/Find mode (BRD input)

/doc-prd-autopilot BRD-01 # Generates PRD-01 if missing, reviews if exists

Review mode (PRD input)

/doc-prd-autopilot PRD-01 # Reviews existing PRD-01

Multiple specific BRDs (generate/find)

/doc-prd-autopilot BRD-01,BRD-02,BRD-05

Multiple specific PRDs (review)

/doc-prd-autopilot PRD-01,PRD-02,PRD-05

All available BRDs

/doc-prd-autopilot all

Pattern match (foundation modules)

/doc-prd-autopilot BRD-0[1-7]

Step 2: Dependency Analysis & Creation Order

The autopilot analyzes cross-BRD dependencies to determine optimal PRD creation order.

Dependency Sources:

Explicit References: @depends-brd: BRD-NN tags in BRD documents
Cross-BRD References: References to other BRDs in Traceability sections
Module Dependencies: Foundation module (F1-F7) vs Domain module (D1-D7) hierarchy
Platform vs Feature: Platform BRDs before Feature BRDs

Algorithm:

def analyze_dependencies(brd_list): """ 1. Build directed graph of BRD dependencies 2. Detect circular dependencies (error if found) 3. Perform topological sort 4. Group independent BRDs for parallel processing 5. Return ordered execution plan """ graph = build_dependency_graph(brd_list)

if has_cycle(graph):
    raise CircularDependencyError()

sorted_order = topological_sort(graph)
parallel_groups = identify_independent_groups(sorted_order)

return ExecutionPlan(sorted_order, parallel_groups)

Output Example:

Dependency Analysis Complete: ├── Execution Order: BRD-06 → BRD-07 → [BRD-01, BRD-02] → BRD-03 → BRD-04 → BRD-05 ├── Parallel Groups: │ ├── Group 1: [BRD-06] (Infrastructure) │ ├── Group 2: [BRD-07] (Config) │ ├── Group 3: [BRD-01, BRD-02] (Parallel - no dependencies) │ ├── Group 4: [BRD-03] (depends on BRD-01) │ └── Group 5: [BRD-04, BRD-05] (Parallel - depend on BRD-03) └── Estimated Time: Sequential 7 units, Parallel 4 units

Step 3: PRD-Ready Score Validation

Before generating a PRD, validate that the source BRD meets PRD-Ready requirements.

Skill Delegation: This phase uses validation rules from doc-brd-audit skill (unified BRD quality gate). See: .claude/skills/doc-brd-audit/SKILL.md for complete BRD validation rules.

PRD-Ready Scoring Criteria (100%):

Category Weight Criteria

Business Requirements Completeness 40% All 18 BRD sections present, objectives defined, stakeholders identified

Technical Readiness 30% Architecture Decision Requirements section complete, technology prerequisites documented

Business Alignment 20% Success criteria quantified, risks assessed, constraints documented

Traceability 10% Strategy references included, downstream placeholders defined

Minimum Score: 90% (configurable)

Auto-Fix Actions:

Issue Auto-Fix Action

Missing timing profiles (p50/p95/p99) Add template timing table

Pending ADR topics without elaboration Add business driver and constraints placeholders

Missing threshold registry Add Appendix with threshold template

Incomplete Document Control Add missing required fields

Missing section numbers Renumber sections sequentially

Validation Command (internal):

python ai_dev_ssd_flow/scripts/validate_prd_ready.py
--brd docs/01_BRD/BRD-01_f1_iam/
--min-score 90
--auto-fix

Step 4: PRD Generation

Generate the PRD document from the validated BRD with real-time quality feedback.

Skill Delegation: This phase follows rules defined in doc-prd skill. See: .claude/skills/doc-prd/SKILL.md for complete PRD creation guidance.

Quality Guidance: Uses quality-advisor skill for real-time feedback during generation. See: .claude/skills/quality-advisor/SKILL.md for quality monitoring.

Generation Process:

Load BRD Content:

Read all BRD section files (for sectioned BRDs)
Extract business requirements, objectives, stakeholders
Parse Architecture Decision Requirements topics

Template Selection (per doc-prd skill):

MVP Template (standard): ai_dev_ssd_flow/02_PRD/PRD-MVP-TEMPLATE.md (21 sections, ≥90% thresholds)
Section Templates: For sectioned PRDs (>25KB)
Note: MVP template IS the standard. Expansion through NEW iterations (PRD-02, PRD-03).
Section Mapping (BRD → PRD):

BRD Section PRD Section(s)

Document Control
Document Control
Executive Summary
Executive Summary
Business Context
Problem Statement
Stakeholder Analysis
Target Audience & User Personas
Business Requirements
Goals & Objectives, 9. Functional Requirements
Success Criteria
Success Metrics (KPIs)
Constraints
Constraints & Assumptions
Architecture Decision Requirements
Traceability (Architecture Decision Requirements)
Risk Assessment
Risk Assessment
Traceability
Traceability

PRD-Specific Content Generation:

Section 7: Scope & Requirements (derive from BRD scope)
Section 8: User Stories & User Roles (extract from stakeholders)
Section 10: Customer-Facing Content & Messaging (MANDATORY)
Section 11: Acceptance Criteria (from BRD success criteria)
Section 14: Success Definition (go-live criteria)
Section 15: Stakeholders & Communication
Section 16: Implementation Approach
Section 17: Budget & Resources
Section 19: References
Section 20: EARS Enhancement Appendix (timing, boundary, state, fallback)
Section 21: Quality Assurance & Testing Strategy

Real-Time Quality Feedback (via quality-advisor skill):

Monitor section completion as content is generated
Detect anti-patterns (AP-001 to AP-017) during creation
Validate cumulative tagging (@brd requirement for Layer 2)
Check element ID format compliance (PRD.NN.TT.SS)
Flag issues early to reduce post-generation rework

Traceability Tags:

@brd: BRD.01.01.01, BRD.01.01.02, BRD.01.23.01

File Output (ALWAYS use nested folder):

Monolithic (<20k tokens): docs/02_PRD/PRD-NN_{slug}/PRD-NN_{slug}.md
Sectioned (≥20k tokens): docs/02_PRD/PRD-NN_{slug}/PRD-NN.0_index.md , PRD-NN.1_core.md , etc.
Master Index (always): docs/02_PRD/PRD-00_index.md (create or update)

Nested Folder Rule: ALL PRDs use nested folders (PRD-NN_{slug}/ ) regardless of size. This keeps companion files (review reports, fix reports, drift cache) organized with their parent document.

Step 5: EARS-Ready Score Validation

After PRD generation, validate EARS-Ready score.

Skill Delegation: This phase uses validation rules from doc-prd-validator skill. See: .claude/skills/doc-prd-validator/SKILL.md for complete validation rules and error codes.

EARS-Ready Scoring Criteria (100%):

Category Weight Criteria

Business Requirements Clarity 40% SMART objectives, functional requirements, acceptance criteria

Requirements Maturity 35% System boundaries, stakeholder requirements, problem statement

EARS Translation Readiness 20% User journeys, quality attributes quantified, timing profiles

Strategic Alignment 5% Domain-specific business logic references

Minimum Score: 90% (standard threshold for all readiness scores)

Auto-Fix Actions (per doc-prd-validator error codes):

Issue Error Code Auto-Fix Action

Missing timing profile matrix PRD-W002 Add Section 20.1 template

Missing boundary value matrix PRD-W002 Add Section 20.2 template

Missing state transition diagram PRD-W002 Add Section 20.3 Mermaid template

Missing fallback documentation PRD-W002 Add Section 20.4 template

Incomplete customer-facing content PRD-E006 Flag for manual review (Section 10)

Blocking Diagram Contract Gate:

Autopilot must fail Phase 4 when any of these codes are present:
PRD-E023 (missing @diagram: c4-l2 )
PRD-E024 (missing @diagram: dfd-l1 )
PRD-E025 (missing @diagram: sequence-* )
PRD-E026 (sequence diagram missing alt/else exception path)

Blocking Element Code Contract Gate:

Autopilot must fail Phase 4 when element type codes violate naming standards:
PRD-E020 (element type code not valid for PRD)
PRD-E022 (section-element type code mismatch)
Section-element mapping enforcement (e.g., Section 5 metrics must use type 08 )

Report Requirement:

Include Diagram Contract Compliance: PASS/FAIL in phase summary output.
Include Element Code Compliance: PASS/FAIL in phase summary output.

Step 6: Review & Fix Cycle (v2.3)

Iterative review and fix cycle to ensure PRD quality before completion.

flowchart TD A[Phase 5 Start] --> B[Run doc-prd-audit] B --> C[Generate Combined Audit Report] C --> D{Review Score >= 90?}

D -->|Yes| E[PASS - Proceed to Phase 6]
D -->|No| F{Iteration &#x3C; Max?}

F -->|Yes| G[Run doc-prd-fixer]
G --> H[Apply Fixes]
H --> I[Generate Fix Report]
I --> J[Increment Iteration]
J --> B

F -->|No| K[Flag for Manual Review]
K --> L[Generate Final Report with Remaining Issues]
L --> E

5.1 Initial Review

Run doc-prd-audit to execute validator + reviewer and generate a combined report.

/doc-prd-audit PRD-NN

Output: PRD-NN.A_audit_report_v001.md (compatibility: reviewer report may still be produced)

Review Checklist:

Check Description Auto-Fix Manual

Link Integrity All internal links between sections resolve Yes

Threshold Consistency Performance metrics match across sections Yes

BRD Alignment PRD content accurately reflects BRD requirements

Review

Placeholder Detection No [TODO] , [TBD] , YYYY-MM-DD remaining Yes

Traceability Tags All @brd: tags reference valid BRD IDs Yes

Cross-Reference Validity @depends: and @discoverability: tags valid Yes

Section Completeness No empty or stub sections

Flag

Customer Content Section 10 has substantive content

Flag

5.2 Fix Cycle

If review score < 90%, invoke doc-prd-fixer .

/doc-prd-fixer PRD-NN --revalidate

Fix Categories:

Category Fixes Applied

Missing Files Create glossary, reference docs

Broken Links Update paths, create targets

Element IDs Convert legacy patterns, fix invalid type codes

Content Replace template placeholders, dates

References Update traceability tags

Thresholds Align inconsistent values to BRD source

Output: PRD-NN.F_fix_report_v001.md

doc-prd-fixer input compatibility:

Preferred: PRD-NN.A_audit_report_vNNN.md
Legacy: PRD-NN.R_review_report_vNNN.md

5.3 Re-Review

After fixes, automatically re-run reviewer.

/doc-prd-audit PRD-NN

Output: PRD-NN.A_audit_report_v002.md

5.4 Iteration Control

Parameter Default Description

max_iterations

3 Maximum fix-review cycles

target_score

90 Minimum passing score

stop_on_manual

false Stop if only manual issues remain

Iteration Example:

Iteration 1: Review v001: Score 85 (2 errors, 4 warnings) Fix v001: Fixed 5 issues, created 1 file

Iteration 2: Review v002: Score 94 (0 errors, 2 warnings) Status: PASS (score >= 90)

5.5 Quality Checks (Post-Fix)

After passing the fix cycle:

Link Integrity Check:

Scanning PRD-01 for internal links... ├── PRD-01.0_index.md: 17 links found │ ├── PRD-01.1_document_control.md ✓ │ ├── PRD-01.2_executive_summary.md ✓ │ └── ... (all valid) └── Result: 0 broken links

Threshold Consistency Check:

Comparing thresholds across sections... ├── Section 5 (Success Metrics): auth.p99 = 100ms ├── Section 9 (Quality Attributes): auth.p99 = 100ms ├── Section 17 (Appendix B.1): auth.p99 = 100ms └── Result: Consistent ✓

BRD Alignment Check:

Verifying PRD requirements map to BRD source... ├── PRD.01.01.01 → BRD.01.01.01 (Multi-Provider Auth) ✓ ├── PRD.01.01.02 → BRD.01.01.02 (4D Authorization) ✓ └── Result: 12/12 requirements aligned ✓

EARS-Ready Report:

EARS-Ready Score Breakdown

Business Requirements Clarity: 40/40 Requirements Maturity: 35/35 EARS Translation Readiness: 20/20 Strategic Alignment: 5/5

Total EARS-Ready Score: 100/100 (Target: >= 90) Status: READY FOR EARS GENERATION

Traceability Matrix Update:

Update PRD-00_TRACEABILITY_MATRIX.md

python ai_dev_ssd_flow/scripts/update_traceability_matrix.py

--prd docs/02_PRD/PRD-NN_{slug}/PRD-NN_{slug}.md

--matrix docs/02_PRD/PRD-00_TRACEABILITY_MATRIX.md

Step 7: Process Next BRD

After completing one PRD:

Mark current BRD→PRD as complete
Update traceability matrix
Move to next BRD in execution order
Repeat Steps 3-5

Progress Tracking:

PRD Generation Progress: [████████░░░░░░░░] 3/7 Complete

Completed: ✓ PRD-06 (from BRD-06) - EARS-Ready: 94% ✓ PRD-07 (from BRD-07) - EARS-Ready: 92% ✓ PRD-01 (from BRD-01) - EARS-Ready: 96%

In Progress: ⟳ PRD-02 (from BRD-02) - Generating Section 10...

Pending: ○ PRD-03 (from BRD-03) - Awaiting BRD-01 completion ○ PRD-04 (from BRD-04) ○ PRD-05 (from BRD-05)

Step 8: Parallel Generation

For independent BRDs (no cross-dependencies), generate PRDs in parallel.

Parallel Execution Rules:

Independence Check: No shared @depends-brd references
Resource Limits: Maximum 3 parallel generations (configurable)
Failure Isolation: One failure doesn't block others
Progress Reporting: Aggregate status updates

Parallel Execution Example:

Parallel Group Execution: ├── Thread 1: BRD-01 → PRD-01 [████████████████] 100% ├── Thread 2: BRD-02 → PRD-02 [████████████░░░░] 75% └── Thread 3: BRD-05 → PRD-05 [████████░░░░░░░░] 50%

Configuration

Default Configuration

# config/prd_autopilot.yaml
prd_autopilot:
  version: "1.2"

  scoring:
    prd_ready_min: 90
    ears_ready_min: 90
    review_score_min: 90
    strict_mode: false

  execution:
    max_parallel: 3
    auto_fix: true
    continue_on_error: false
    timeout_per_brd: 300  # seconds

  output:
    structure: auto  # auto, monolithic, sectioned
    size_threshold_kb: 25
    report_format: markdown

  validation:
    skip_validation: false
    fix_iterations_max: 3

  review:
    enabled: true
    check_links: true
    check_thresholds: true
    check_brd_alignment: true
    check_placeholders: true
    check_traceability: true
    auto_fix_links: true
    auto_fix_placeholders: true
    flag_customer_content: true

Command Line Options

Option
Default
Description

--min-prd-ready

90
Minimum PRD-Ready score

--min-ears-ready

90
Minimum EARS-Ready score

--min-review-score

90
Minimum Final Review score

--max-parallel

3
Maximum parallel PRD generations

--no-auto-fix

false
Disable auto-fix (manual only)

--continue-on-error

false
Continue if one BRD fails

--dry-run

false
Preview execution plan only

--output-format

auto
Force monolithic or sectioned output

--skip-review

false
Skip final content review phase

--review-only

false
Run only final review on existing PRD

Context Management

Chunked Parallel Execution (MANDATORY)

CRITICAL: To prevent conversation context overflow errors ("Prompt is too long", "Conversation too long"), all autopilot operations MUST follow chunked execution rules:

Chunk Size Limit: Maximum 3 documents per chunk

Chunking Rules:

- Chunk Formation: Group documents into chunks of maximum 3 documents each

- Sequential Chunk Processing: Process one chunk at a time, completing all documents in a chunk before starting the next

- Context Pause: After completing each chunk, provide a summary and pause for user acknowledgment

- Progress Tracking: Display chunk progress (e.g., "Chunk 2/5: Processing BRD-04, BRD-05, BRD-06")

Execution Pattern:

Documents: BRD-01, BRD-02, BRD-03, BRD-04, BRD-05, BRD-06, BRD-07

Chunk 1: [BRD-01, BRD-02, BRD-03] → Process → Summary → Pause
Chunk 2: [BRD-04, BRD-05, BRD-06] → Process → Summary → Pause
Chunk 3: [BRD-07]                  → Process → Summary → Complete

Chunk Completion Summary Template:

Chunk N/M Complete:
├── Generated: PRD-01, PRD-02, PRD-03
├── EARS-Ready Scores: 94%, 92%, 91%
├── Status: All validated
└── Next: Continue with Chunk N+1? [Y/n]

Why Chunking is Required:

- Prevents "Conversation too long" errors during batch processing

- Allows context compaction between chunks

- Enables recovery from failures without losing all progress

- Provides natural checkpoints for user review

Configuration Override:

execution:
  max_parallel: 3        # HARD LIMIT - do not exceed
  chunk_size: 3          # Documents per chunk
  pause_between_chunks: true

Execution Modes

Mode 1: Interactive (Default)

User confirms each step before proceeding.

/doc-prd-autopilot BRD-01,BRD-02 --interactive

# Output:
# Dependency Analysis: BRD-01 → BRD-02 (BRD-02 depends on BRD-01)
#
# [1/2] BRD-01: PRD-Ready Score = 92% (PASS)
# Generate PRD-01? [Y/n] y
# PRD-01 generated. EARS-Ready Score = 94% (PASS)
#
# [2/2] BRD-02: PRD-Ready Score = 88% (FAIL)
# Auto-fix available. Apply fixes? [Y/n] y
# Fixes applied. New score = 91% (PASS)
# Generate PRD-02? [Y/n] y
# PRD-02 generated. EARS-Ready Score = 90% (PASS)
#
# Summary: 2/2 PRDs generated successfully.

Mode 2: Automatic

No user confirmation, auto-fix enabled.

/doc-prd-autopilot all --auto

# Output:
# PRD Autopilot - Automatic Mode
# ==============================
# Scanning: docs/01_BRD/
# Found: 7 BRDs
#
# Phase 1: Dependency Analysis... Done
# Phase 2-4: Processing...
#   [████████████████] 7/7 Complete
#
# Summary:
#   ✓ 7 PRDs generated
#   ✓ 3 BRDs auto-fixed
#   ✓ Average EARS-Ready: 93%

Mode 3: Dry Run

Preview execution plan without generating files.

/doc-prd-autopilot all --dry-run

# Output:
# PRD Autopilot - Dry Run Mode
# ============================
#
# Execution Plan:
# 1. BRD-06 (Infrastructure) → PRD-06
# 2. BRD-07 (Config) → PRD-07
# 3. [Parallel] BRD-01, BRD-02 → PRD-01, PRD-02
# 4. BRD-03 → PRD-03
# 5. [Parallel] BRD-04, BRD-05 → PRD-04, PRD-05
#
# Estimated Duration: ~4 units (parallel) vs ~7 units (sequential)
#
# No files will be created in dry-run mode.

Mode 4: Review Mode (v2.2)

Validate existing PRD documents and generate a quality report without modification.

Purpose: Audit existing PRD documents for compliance, quality scores, and identify issues.

Command:

# Review single PRD
/doc-prd-autopilot PRD-01 --mode review

# Review all PRDs
/doc-prd-autopilot all --mode review --output-report tmp/prd_review_report.md

MANDATORY Actions in Review Mode:

- Run doc-prd-audit
 - Execute full audit (NOT just read existing reports)

- Create/Update .drift_cache.json
 - Track upstream BRD changes

- Generate audit report - Write PRD-NN.A_audit_report_vNNN.md

WARNING: Reading existing audit reports without running fresh audits is a skill violation. Each review invocation MUST produce fresh validation and update drift tracking.

Review Report Structure:

# PRD Review Report: PRD-01_f1_iam

## Summary
- **EARS-Ready Score**: 87% 🟡
- **Final Review Score**: 85% 🟡
- **Total Issues**: 14
- **Auto-Fixable**: 10
- **Manual Review**: 4

## Score Breakdown
| Category | Score | Status |
|----------|-------|--------|
| Business Requirements Clarity | 38/40 | 🟡 |
| Requirements Maturity | 32/35 | 🟡 |
| EARS Translation Readiness | 18/20 | 🟡 |
| Strategic Alignment | 5/5 | ✅ |

## Final Review Checks
| Check | Status | Details |
|-------|--------|---------|
| Link Integrity | ✅ | All links valid |
| Threshold Consistency | 🟡 | 2 mismatches found |
| BRD Alignment | ✅ | All requirements traced |
| Placeholder Detection | ❌ | 3 [TODO] markers found |
| Traceability Tags | ✅ | Valid @brd references |
| Section 10 Content | 🟡 | Needs business review |

## Auto-Fixable Issues
| # | Issue | Location | Fix Action |
|---|-------|----------|------------|
| 1 | Legacy element ID | Section 9:L45 | Convert PO-001 to PRD.01.07.01 |
| 2 | Placeholder text | Section 14:L78 | Remove [TODO] marker |
| 3 | Inconsistent threshold | Section 5:L23 | Align to BRD value |
| ... | ... | ... | ... |

## Manual Review Required
| # | Issue | Location | Reason |
|---|-------|----------|--------|
| 1 | Incomplete Section 10 | Customer-Facing Content | Requires business input |
| 2 | Missing timing profile | Section 20.1 | Domain expertise needed |
| ... | ... | ... | ... |

Review Configuration:

review_mode:
  enabled: true
  checks:
    - structure_validation      # 21 sections
    - element_id_compliance     # PRD.NN.TT.SS format
    - link_integrity            # Internal link check
    - threshold_consistency     # Cross-section consistency
    - brd_alignment             # Upstream traceability
    - placeholder_detection     # [TODO], [TBD] markers
    - traceability_tags         # @brd tag validation
    - section_10_content        # Customer-facing content
    - score_calculation         # EARS-Ready score
  output:
    format: markdown
    include_fix_suggestions: true
  thresholds:
    pass: 90
    warning: 85
    fail: 0

Mode 5: Fix Mode (v2.1)

Auto-repair existing PRD documents while preserving manual content.

Purpose: Apply automated fixes to PRD documents to improve quality scores and compliance.

Command:

# Fix single PRD
/doc-prd-autopilot PRD-01 --mode fix

# Fix with backup
/doc-prd-autopilot PRD-01 --mode fix --backup

# Fix specific issue types only
/doc-prd-autopilot PRD-01 --mode fix --fix-types "element_ids,thresholds,placeholders"

# Dry-run fix (preview changes)
/doc-prd-autopilot PRD-01 --mode fix --dry-run

Fix Categories and Actions:

Category
Issue
Auto-Fix Action
Preserves Content

Element IDs
Legacy PO-XXX format
Convert to PRD.NN.07.SS
✅

Element IDs
Legacy FF-XXX format
Convert to PRD.NN.01.SS
✅

Element IDs
Legacy AC-XXX format
Convert to PRD.NN.06.SS
✅

Thresholds
Inconsistent values
Align to BRD source
✅

Thresholds
Hardcoded values
Replace with @threshold
✅

Links
Broken internal links
Update paths or remove
✅

Placeholders
[TODO], [TBD] text
Remove markers, flag content
✅

Sections
Missing Document Control
Add from template
✅

Sections
Missing EARS-Ready score
Calculate and insert
✅

Sections
Missing Section 20
Add EARS Enhancement template
✅

Traceability
Missing @brd tags
Add with placeholder
✅

Traceability
Invalid @brd reference
Correct or remove
✅

Content Preservation Rules:

- Never delete existing requirements or user stories

- Never modify executive summary content

- Never change stakeholder analysis details

- Only add missing sections and metadata

- Only replace legacy element IDs and placeholders

- Backup first if --backup
 flag is set

Element ID Migration:

Legacy Pattern
New Format
Example

PO-XXX

PRD.NN.07.SS

PO-001 → PRD.01.07.01

FF-XXX

PRD.NN.01.SS

FF-001 → PRD.01.01.01

AC-XXX

PRD.NN.06.SS

AC-001 → PRD.01.06.01

US-XXX

PRD.NN.08.SS

US-001 → PRD.01.08.01

Fix Report Structure:

# PRD Fix Report: PRD-01_f1_iam

## Summary
- **Before EARS-Ready Score**: 87% 🟡
- **After EARS-Ready Score**: 94% ✅
- **Issues Fixed**: 10
- **Issues Remaining**: 4 (manual review required)

## Fixes Applied
| # | Issue | Location | Fix Applied |
|---|-------|----------|-------------|
| 1 | Legacy element ID | Section 9:L45 | Converted PO-001 → PRD.01.07.01 |
| 2 | Placeholder text | Section 14:L78 | Removed [TODO] marker |
| 3 | Inconsistent threshold | Section 5:L23 | Aligned to BRD.01 value |
| ... | ... | ... | ... |

## Files Modified
- docs/02_PRD/PRD-01_f1_iam/PRD-01.0_index.md
- docs/02_PRD/PRD-01_f1_iam/PRD-01.5_success_metrics.md
- docs/02_PRD/PRD-01_f1_iam/PRD-01.9_functional_requirements.md

## Backup Location
- tmp/backup/PRD-01_f1_iam_20260209_143022/

## Score Impact
| Category | Before | After | Delta |
|----------|--------|-------|-------|
| Requirements Clarity | 38/40 | 40/40 | +2 |
| Requirements Maturity | 32/35 | 34/35 | +2 |
| EARS Translation | 18/20 | 19/20 | +1 |

## Next Steps
1. Complete Section 10 (Customer-Facing Content)
2. Add timing profile to Section 20.1
3. Re-run validation to confirm score

Fix Configuration:

fix_mode:
  enabled: true
  backup:
    enabled: true
    location: "tmp/backup/"
    retention_days: 7

  fix_categories:
    element_ids: true        # Legacy ID conversion
    thresholds: true         # Consistency fixes
    links: true              # Broken link repair
    placeholders: true       # [TODO]/[TBD] removal
    sections: true           # Missing sections
    traceability: true       # @brd tag fixes

  preservation:
    executive_summary: true     # Never modify
    requirements: true          # Never delete
    user_stories: true          # Never modify
    comments: true              # Preserve user comments

  validation:
    re_validate_after_fix: true
    require_score_improvement: false
    max_fix_iterations: 3

  element_id_migration:
    PO_XXX_to_PRD_NN_07_SS: true
    FF_XXX_to_PRD_NN_01_SS: true
    AC_XXX_to_PRD_NN_06_SS: true
    US_XXX_to_PRD_NN_08_SS: true

Command Line Options (Review/Fix):

Option
Mode
Default
Description

--mode review

Review
-
Run review mode only

--mode fix

Fix
-
Run fix mode

--output-report

Both
auto
Report output path

--backup

Fix
true
Create backup before fixing

--fix-types

Fix
all
Comma-separated fix categories

--dry-run

Fix
false
Preview fixes without applying

--preserve-all

Fix
false
Extra cautious preservation

Output Files

Generated PRD Structure

Nested Folder Rule: ALL PRDs use nested folders (PRD-NN_{slug}/
) regardless of size.

Monolithic Output (single file ≤25KB - in nested folder):

docs/02_PRD/
├── PRD-00_TRACEABILITY_MATRIX.md  # Updated
└── PRD-01_f1_iam/                  # Nested folder (REQUIRED)
    └── PRD-01_f1_iam.md            # Monolithic PRD inside folder

Sectioned Output (multiple files >25KB - in nested folder):

docs/02_PRD/
├── PRD-00_TRACEABILITY_MATRIX.md  # Updated
└── PRD-01_f1_iam/                  # Nested folder (REQUIRED)
    ├── PRD-01.0_index.md
    ├── PRD-01.1_document_control.md
    ├── PRD-01.2_executive_summary.md
    ├── PRD-01.3_problem_statement.md
    ...
    └── PRD-01.21_qa_strategy.md

Summary Report

Generated after completion:

# PRD Autopilot Summary Report

**Execution Date**: 2026-02-08
**Input**: 7 BRDs
**Output**: 7 PRDs

## Execution Order

| Step | BRD | PRD | PRD-Ready | EARS-Ready | Duration | Status |
|------|-----|-----|-----------|------------|----------|--------|
| 1 | BRD-06 | PRD-06 | 94% | 92% | 45s | Success |
| 2 | BRD-07 | PRD-07 | 91% | 90% | 52s | Success |
| 3 | BRD-01 | PRD-01 | 96% | 96% | 48s | Success |
| 3 | BRD-02 | PRD-02 | 92% | 91% | 47s | Success (Parallel) |
| 4 | BRD-03 | PRD-03 | 90% | 93% | 50s | Success |
| 5 | BRD-04 | PRD-04 | 88%→91% | 90% | 62s | Success (Auto-fixed) |
| 5 | BRD-05 | PRD-05 | 93% | 94% | 44s | Success (Parallel) |

## Auto-Fixes Applied

| BRD | Issue | Fix Applied |
|-----|-------|-------------|
| BRD-04 | Missing timing profiles | Added p50/p95/p99 table |
| BRD-04 | Pending ADR topic | Added business driver |

## Next Steps

1. Review generated PRDs for domain-specific content
2. Complete Section 10 (Customer-Facing Content) manually if flagged
3. Run `/doc-ears-autopilot` to generate EARS from PRDs

Error Handling

Common Errors

Error
Cause
Resolution

CircularDependencyError

BRD-A depends on BRD-B and vice versa
Review and remove circular reference

BRDNotFoundError

Specified BRD does not exist
Check path and BRD ID

PRDReadyScoreLow

BRD score &#x3C; 90% after auto-fix attempts
Manual BRD improvement required

EARSReadyScoreLow

PRD score &#x3C; 90% after auto-fix
Manual PRD improvement required

TemplateNotFoundError

PRD template missing
Verify ai_dev_ssd_flow/02_PRD/
 exists

Recovery Actions

# Resume from last successful point
/doc-prd-autopilot resume

# Skip failed BRD and continue
/doc-prd-autopilot all --continue-on-error

# Retry single failed BRD
/doc-prd-autopilot BRD-04 --force

Integration with Other Skills

Upstream Skills

- doc-brd
: Create/update BRDs before running autopilot

- doc-validator
: Pre-validate BRDs for readiness

Downstream Skills

- doc-ears-autopilot
: Chain autopilot for EARS generation (future)

- doc-ears
: Manual EARS creation from PRDs

- doc-prd
: Manual PRD editing after autopilot

Typical Workflow

1. doc-brd (create BRDs)
2. doc-prd-autopilot (generate PRDs) ← This skill
3. doc-ears (create EARS from PRDs)
4. doc-bdd (create BDD from EARS)
5. ... continue SDD workflow

Prerequisites

Before using this skill, ensure:

- BRD Documents Exist: At least one BRD in docs/01_BRD/

- Templates Available: ai_dev_ssd_flow/02_PRD/PRD-MVP-TEMPLATE.md

- Shared Standards: .claude/skills/doc-flow/SHARED_CONTENT.md

Pre-Flight Check

# Verify BRD directory
ls docs/01_BRD/

# Verify PRD template
ls ai_dev_ssd_flow/02_PRD/PRD-MVP-TEMPLATE.md

# Check for existing PRDs
ls docs/02_PRD/ 2>/dev/null || echo "PRD directory will be created"

Validation Checklist

After autopilot completion:

-  All target PRDs generated

-  Each PRD has EARS-Ready score >= 90%

-  Each PRD has Final Review score >= 90%

-  Traceability matrix updated (PRD-00_TRACEABILITY_MATRIX.md
)

-  Each PRD references upstream BRD with @brd
 tags

-  Section 10 (Customer-Facing Content) has substantive content

-  Section 20 (EARS Enhancement Appendix) completed

-  No broken links in generated documents (verified by Final Review)

-  No placeholder text remaining (verified by Final Review)

-  Thresholds consistent across sections (verified by Final Review)

-  BRD alignment verified (all PRD requirements trace to BRD source)

-  Drift cache created (.drift_cache.json
 in each PRD folder)

Quick Reference

Input
Output
Key Metric

BRD(s)
PRD(s)
EARS-Ready >= 90%

Usage:

/doc-prd-autopilot &#x3C;BRD-LIST> [OPTIONS]

Common Commands:

# Single BRD
/doc-prd-autopilot BRD-01

# All BRDs (automatic)
/doc-prd-autopilot all --auto

# Preview only
/doc-prd-autopilot all --dry-run

# Resume after failure
/doc-prd-autopilot resume

Related Resources

Skills (Delegated)

- PRD Skill: .claude/skills/doc-prd/SKILL.md
 - PRD creation rules and structure

- PRD Validator Skill: .claude/skills/doc-prd-validator/SKILL.md
 - Validation rules and error codes

- BRD Audit Skill: .claude/skills/doc-brd-audit/SKILL.md
 - Unified BRD quality gate (replaces deprecated doc-brd-validator)

Templates and Rules

- PRD Template: ai_dev_ssd_flow/02_PRD/PRD-MVP-TEMPLATE.md

- PRD Schema: ai_dev_ssd_flow/02_PRD/PRD_MVP_SCHEMA.yaml

- PRD Creation Rules: ai_dev_ssd_flow/02_PRD/PRD_MVP_CREATION_RULES.md

- PRD Validation Rules: ai_dev_ssd_flow/02_PRD/PRD_MVP_VALIDATION_RULES.md

Framework References

- SDD Workflow: ai_dev_ssd_flow/SPEC_DRIVEN_DEVELOPMENT_GUIDE.md

- MVP Autopilot: ai_dev_ssd_flow/AUTOPILOT/MVP_AUTOPILOT.md

Review Document Standards (v2.2)

IMPORTANT: Review reports generated by this autopilot are formal project documents.

See: .claude/skills/REVIEW_DOCUMENT_STANDARDS.md
 for complete standards.

Quick Reference

Requirement
Value

Storage Location
Same folder as reviewed PRD

File Name
PRD-NN.A_audit_report_vNNN.md
 (preferred), PRD-NN.R_review_report_vNNN.md
 (legacy)

YAML Frontmatter
MANDATORY - see shared standards

Parent Reference
MANDATORY - link to PRD index

Example Location (ALL PRDs use nested folders):

docs/02_PRD/PRD-03_f3_observability/        # Nested folder (REQUIRED)
├── PRD-03_f3_observability.md              # Monolithic PRD
├── PRD-03.A_audit_report_v001.md           # Combined audit report v001
├── PRD-03.A_audit_report_v002.md           # Combined audit report v002
├── PRD-03.F_fix_report_v001.md             # Fix report (if fixes applied)
└── .drift_cache.json                        # Drift cache

docs/02_PRD/PRD-04_f4_config/               # Sectioned PRD example
├── PRD-04.0_index.md                        # Index file
├── PRD-04.1_core.md
├── PRD-04.A_audit_report_v001.md           # Combined audit report
└── .drift_cache.json                        # Drift cache

Version History

Version
Date
Changes

2.9
2026-03-02
Drift Cache Creation Enforcement (MANDATORY): Added "Review Mode Mandatory Steps" section; Updated Action Determination Output to use doc-prd-audit
 instead of doc-prd-reviewer
; Added drift cache to validation checklist; Updated Mode 4: Review Mode (v2.2) with mandatory audit execution and drift cache creation warnings

2.8
2026-03-02
Element Code Contract Gate (BLOCKING): Added element type code validation as blocking gate in Phase 4; PRD-E020/PRD-E022 now fail autopilot; Added section-element mapping enforcement; Report must include Element Code Compliance status

2.7
2026-03-01
2-Skill BRD Model: Updated BRD validation references from doc-brd-validator
 to doc-brd-audit
 (unified quality gate)

2.6
2026-02-26
Migrated frontmatter to metadata
; switched PRD references to ai_dev_ssd_flow
; integrated doc-prd-audit
 in Phase 5 with combined report compatibility (.A_audit_report
 preferred, .R_review_report
 legacy)

2.5
2026-02-11
Smart Document Detection: Added automatic document type recognition; Self-type input (PRD-NN) triggers review mode; Upstream-type input (BRD-NN) triggers generate-if-missing or find-and-review; Updated input patterns table with type-based actions

2.4
2026-02-11
Nested Folder Enforcement: Fixed output structure examples to show ALL PRDs in nested folders regardless of size; Removed incorrect non-nested monolithic PRD example; Updated review report location examples

2.3
2026-02-10
Review &#x26; Fix Cycle: Replaced Phase 5 (Step 6) with iterative Review -> Fix cycle using doc-prd-reviewer
 and doc-prd-fixer
; Added doc-prd-fixer
 skill dependency; Added iteration control with max 3 cycles and 90% target score

2.2
2026-02-10
Added Review Document Standards: review reports stored alongside reviewed documents with YAML frontmatter and parent references; references shared .claude/skills/REVIEW_DOCUMENT_STANDARDS.md

2.1
2026-02-09
Added Mode 4: Review Mode for validation-only analysis with visual score indicators; Added Mode 5: Fix Mode for auto-repair with backup and content preservation; Element ID migration (PO-XXX→PRD.NN.07.SS, FF-XXX→PRD.NN.01.SS, AC-XXX→PRD.NN.06.SS, US-XXX→PRD.NN.08.SS)

1.3
2026-02-08
Integrated quality-advisor skill for real-time quality feedback in Phase 3 (PRD Generation)

1.2
2026-02-08
Added Phase 5: Final Content Review with link integrity, threshold consistency, BRD alignment, and placeholder detection checks

1.1
2026-02-08
Added skill dependencies, integrated doc-prd and doc-prd-validator skills

1.0
2026-02-08
Initial skill creation with 7-step workflow