Validation Pipeline

Validation Pipeline

Purpose

Run structured validation pipelines that execute steps sequentially, enforce gates at blocking failures, and produce scored reports. Uses the src/validation/pipeline.ts framework with 13 requirements validation steps (BMAD-003).

Activation

• When validating requirements documents
• When running structured quality gates
• When assessing document completeness, testability, or traceability
• When invoked via /validation-pipeline

Quick Start

# Validate a requirements document (all 13 steps)
/validation-pipeline requirements docs/requirements.md

# Validate with specific steps only
/validation-pipeline requirements docs/requirements.md --steps format-check,completeness-check,invest-criteria

# Continue past blocking failures
/validation-pipeline requirements docs/requirements.md --continue-on-failure

# Output as JSON
/validation-pipeline requirements docs/requirements.md --json

Workflow

Step 1: Read the Target Document

Read the file specified by the user. If no file is provided, ask for one.

Read the target document using the Read tool.
Store the content for pipeline execution.

Step 2: Select Pipeline

Choose the appropriate pipeline based on the user's request:

Pipeline	Steps	Use Case
requirements	13	Requirements documents, PRDs, user stories

Additional pipelines can be created by defining new step sets in src/validation/steps/.

Step 3: Execute Pipeline

The pipeline framework (src/validation/pipeline.ts) handles execution:

1. Sequential execution — steps run in order, each receiving results from prior steps
2. Gate enforcement — blocking steps that fail halt the pipeline (unless --continue-on-failure)
3. Per-step scoring — each step produces a 0-100 score with findings and evidence
4. Weighted rollup — overall score uses category weights (format=10%, content=30%, quality=25%, traceability=20%, compliance=15%)