review-cross-artifact

To check traceability across SPEC.md, REQUIREMENTS.md, ROADMAP.md, and DESIGN.md, invoke a cross-artifact reviewer to validate mappings, detect unmapped acceptance criteria, and identify orphaned requirements or missing design coverage.

Cross-artifact alignment is the consistency check between planning documents like SPEC.md and ROADMAP.md to prevent gaps. It ensures every requirement maps to design coverage and roadmap phases, preventing phantom requirements and lifecycle gaps.

You detect orphaned requirements and missing design coverage by running a two-pass review loop on your planning artifacts. This process validates that all acceptance criteria map correctly and flags unmapped items as structured ISSUES_FOUND findings.

Yes, cross-artifact review outputs structured PASS or ISSUES_FOUND findings suitable for automated dashboards. It enforces a two-pass review loop to return consistent, machine-readable results for auditing and lifecycle automation.

You can validate cross-artifact mappings automatically by passing SPEC.md, REQUIREMENTS.md, ROADMAP.md, and DESIGN.md file paths to the reviewer. It programmatically detects inconsistencies and unmapped acceptance criteria without manual comparison.

You need cross-artifact consistency checks when managing multiple planning documents simultaneously to prevent traceability gaps. It is required when unmapped acceptance criteria, orphaned requirements, or missing design coverage threaten project alignment.