Validate Prd Tech Spec Traceability.prompt

---
description: "Validate PRD-to-tech-spec requirement traceability, score coverage quality, and identify missing or conflicting mappings."
name: "Validate PRD-Tech Spec Traceability"
argument-hint: "Path to PRD and tech spec files"
agent: "agent"
---

Validate traceability between a PRD and a technical specification.

References:
- [Create PRD Skill](../skills/create-prd/SKILL.md)
- [Create Tech Spec Skill](../skills/create-tech-spec/SKILL.md)
- [Tech Spec Template](../skills/create-tech-spec/assets/tech-spec-template.md)

## Scope
- Confirm product requirements are represented by technical decisions.
- Detect missing, partial, or conflicting mappings.
- Highlight overdesign that is not anchored to PRD scope.

## Validation Steps
1. Extract PRD requirement set:
   - Goals
   - In-scope and out-of-scope
   - Functional requirements (`FR-*`)
   - Non-functional requirements (`NFR-*`)
   - Success metrics and constraints
2. Extract corresponding tech spec decisions and sections.
3. Build a requirement-to-decision mapping matrix.
4. Classify each requirement as:
   - `Mapped`
   - `Partially Mapped`
   - `Missing`
   - `Conflicting`
5. Identify technical decisions with no PRD anchor.
6. Score traceability quality and provide remediation.

## Traceability Quality Rubric (0-100)
- Functional requirement coverage (35)
- Non-functional requirement coverage (25)
- Scope fidelity (15)
- Assumptions and open-question handling (10)
- Validation and acceptance readiness (15)

## Mapping Quality Checks
For each PRD requirement, verify:
- Direct mapping to a technical decision/section
- No contradiction with PRD scope or intent
- Adequate technical specificity for implementation planning
- Observable validation path (testability or measurable outcome)

## Output Format
### Traceability Score
- Overall score: <0-100>
- Rating: <Excellent|Good|Needs Work|High Risk>
- Summary: <2-4 sentences>

### Requirement Mapping Matrix
| PRD ID | Requirement Summary | Tech Spec Section/Decision | Status | Notes |
|---|---|---|---|---|
| FR-1 | <summary> | <section> | <Mapped/Partially Mapped/Missing/Conflicting> | <notes> |
| NFR-1 | <summary> | <section> | <Mapped/Partially Mapped/Missing/Conflicting> | <notes> |

### Unanchored Technical Decisions
- <decision with no PRD linkage>

### Priority Fixes
1. <highest-priority fix>
2. <next fix>
3. <next fix>

### Questions to Resolve
- <question 1>
- <question 2>

### Go/No-Go Recommendation
- Recommendation: <Proceed to implementation planning|Revise tech spec first>
- Minimum changes to proceed:
  - <change 1>
  - <change 2>