fix: tighten milestone audit requirements verification with 3-source cross-reference

Closes five gaps where requirements could slip through unchecked at milestone
level: audit now cross-references VERIFICATION.md + SUMMARY frontmatter +
REQUIREMENTS.md traceability, integration checker receives req IDs, gap objects
carry plan-level detail, plan-milestone-gaps updates traceability, and
complete-milestone gates on requirements status.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2026-02-16 14:03:50 -06:00
parent e449c5afa6
commit 2f258956a2
4 changed files with 129 additions and 13 deletions

View File

@@ -123,19 +123,34 @@ Add new phases to current milestone:
...
```
## 7. Create Phase Directories
## 7. Update REQUIREMENTS.md Traceability Table (REQUIRED)
For each REQ-ID assigned to a gap closure phase:
- Update the Phase column to reflect the new gap closure phase
- Reset Status to `Pending`
Reset checked-off requirements the audit found unsatisfied:
- Change `[x]` → `[ ]` for any requirement marked unsatisfied in the audit
- Update coverage count at top of REQUIREMENTS.md
```bash
# Verify traceability table reflects gap closure assignments
grep -c "Pending" .planning/REQUIREMENTS.md
```
## 8. Create Phase Directories
```bash
mkdir -p ".planning/phases/{NN}-{name}"
```
## 8. Commit Roadmap Update
## 9. Commit Roadmap and Requirements Update
```bash
node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs(roadmap): add gap closure phases {N}-{M}" --files .planning/ROADMAP.md
node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs(roadmap): add gap closure phases {N}-{M}" --files .planning/ROADMAP.md .planning/REQUIREMENTS.md
```
## 9. Offer Next Steps
## 10. Offer Next Steps
```markdown
## ✓ Gap Closure Phases Created
@@ -250,7 +265,10 @@ becomes:
- [ ] Gaps grouped into logical phases
- [ ] User confirmed phase plan
- [ ] ROADMAP.md updated with new phases
- [ ] REQUIREMENTS.md traceability table updated with gap closure phase assignments
- [ ] Unsatisfied requirement checkboxes reset (`[x]` → `[ ]`)
- [ ] Coverage count updated in REQUIREMENTS.md
- [ ] Phase directories created
- [ ] Changes committed
- [ ] Changes committed (includes REQUIREMENTS.md)
- [ ] User knows to run `/gsd:plan-phase` next
</success_criteria>