Reading VERIFICATION.md
What gap types mean and how to act on each one — the difference between a missing feature and a partial implementation changes your fix path
advanced/gsd:verify-work creates VERIFICATION.md. Gaps are not failures — they’re a prioritized list of what to address before calling the phase done. Reading them correctly tells you exactly what fix path to take.
Gap types
Each gap in VERIFICATION.md falls into one of four categories:
| Gap type | What it means | Fix path |
|---|---|---|
| Missing feature | Requirement was scoped but executor didn’t implement it | /gsd:plan-phase N --gaps |
| Partial implementation | Feature exists but edge cases are missing | /gsd:plan-phase N --gaps |
| Test failure | Automated tests don’t pass | Debug agent diagnoses root cause |
| Stub/placeholder | Executor left a TODO or placeholder comment | Fix plan targets the stub specifically |
Missing feature and partial implementation share the same fix path — both need targeted gap-closure plans. Test failures and stubs are more surgical and often fixable in a single focused plan.
The fix path
Three commands close gaps without re-doing completed work:
$ /gsd:verify-work 1$ /gsd:plan-phase 1 --gaps$ /gsd:execute-phase 1/gsd:verify-work creates VERIFICATION.md with the gap list. /gsd:plan-phase N --gaps reads that file and creates targeted plans for only the open gaps — it doesn’t touch completed work. /gsd:execute-phase then runs only those gap-closure plans.