/validate-tasks

---

🚨 EXECUTION NOTICE FOR CLAUDE

When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below.

YOU are the executor. This is NOT an autonomous subprocess.

• ✅ The phases below are YOUR execution checklist
• ✅ YOU must run each phase immediately using tools (Bash, Read, Write, Edit, TodoWrite)
• ✅ Complete ALL phases before considering this command done
• ❌ DON't wait for "the command to complete" - YOU complete it by executing the phases
• ❌ DON't treat this as status output - it IS your instruction set

Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.

See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.

---

Arguments: $ARGUMENTS

Goal: Validate that tasks marked complete in tasks.md have corresponding implementation work

Core Principles:

• Verify don't assume - check actual files and git history
• Evidence-based validation - require proof of implementation
• Actionable reporting - provide specific remediation steps

Phase 1: Discovery Goal: Parse spec number and locate task files

Actions:

• Parse $ARGUMENTS for spec number (e.g., "F001", "001", "spec-001")
• Find spec directory (phase-nested first, then legacy): !{bash find specs/phase-* -type f -name "tasks.md" -path "$SPEC_NUMBER" 2>/dev/null | head -1 | xargs dirname || find specs -type f -name "tasks.md" -path "$SPEC_NUMBER" 2>/dev/null | head -1 | xargs dirname}
• Store as SPEC_DIR
• Verify tasks.md exists: !{bash test -f "$SPEC_DIR/tasks.md" && echo "✓ Found" || echo "✗ Missing"}
• If missing, report error and suggest creating tasks.md

Phase 2: Validation Goal: Launch task-validator agent

Actions:

Task(description="Validate task completion", subagent_type="quality:task-validator", prompt="You are the task-validator agent. Validate task completion for spec $ARGUMENTS.

Load the tasks.md file and verify each task marked [x] has:

• Corresponding files that exist
• Git commits related to the task
• Tests covering the functionality
• No uncommitted changes for the feature

Also identify tasks that should be marked complete but aren't.

Generate a comprehensive validation report with:

• ✅ Verified completions (high confidence)
• ⚠️ Questionable completions (needs verification)
• ❌ False completions (no evidence)
• 📝 Completed but not marked

Provide specific file paths, commit SHAs, and remediation steps.")

Phase 3: Summary Goal: Report validation results

Actions:

• Display agent's validation report
• Show health score (% of tasks verified)
• List priority actions
• Suggest next steps:
  • Update tasks.md based on findings
  • Run /quality:test to verify functionality
  • Address false completions immediately