# Step 4 — Validate

Before presenting to the user, verify:
- All template sections (1-6 and Appendix A) are populated or marked "Not applicable" with justification
- Every CSCI has a project-unique identifier and represents a logically cohesive grouping (not a 1:1 service mapping)
- The specification tree (4.1.f) is present and shows relationships among planned specifications
- System-wide design decisions (Section 3) are framed as behavioral responses to requirements — **no tool/product names appear as primary descriptions**
- Interface descriptions (4.3.x) cover all seven aspects (a through g) where applicable
- Requirements traceability (Section 5) covers all system requirements in both directions
- Document is written in {document_output_language}

---

**Requirements Quality Check**: For every requirements section in the generated document (Section 3 system-wide design decisions framed as behavioral responses, Section 4 interface descriptions, Section 5 traceability), apply the `mil498-requirement-quality` skill to audit each requirement against the 14 quality criteria. Present the audit table and any missing elements before the confirmation gate.

---

**CONFIRMATION GATE**: Present the validation results to the user. List any issues found and corrections made. Wait for the user to confirm before proceeding to the review step.
