The /verify command checks if a feature or task is truly complete and meets the defined requirements. This process relies on Walkthrough artifacts (test guides) to ensure no regressions exist before marking a task as Done.
Execution Steps
1. Locate Walkthrough
The system searches artifacts/walkthroughs/ for a relevant guide. If one is missing, the Agent suggests auto-scaffolding a draft based on the Backlog description.
2. Execute Verification Checklist
The Agent performs live checks:
- Build/Test: Runs
npm run buildornpm test. - File Integrity: Confirms newly created files exist.
- Content Validation: Reviews file contents for logic accuracy and compliance.
3. Result Comparison
The system compares the “Actual Output” with the “Expected Output” defined in the walkthrough:
- ✅ Match: Pass.
- ❌ Mismatch: Flag as a regression and request a fix.
4. Log Evidence
Verification results are recorded in the Session Log, specifying the status (Passed/Failed), steps executed, and any found bugs. Finally, it toggles the completion flag in backlog.md.
Relationships
/backlog— Updates task status post-verification./release— Runs full verification before production release./push— Commits and pushes verified code to GitHub.