Flow Validate

Validate Flow project integrity and optionally fix issues.

Phase 1: Directory Structure

Check required files exist:

• .agents/product.md
• .agents/tech-stack.md
• .agents/workflow.md
• .agents/beads.json
• .agents/flows.md
• .agents/patterns.md
• .beads/ directory

---

Phase 2: Beads Health

br version
br status

Check Beads is operational.

---

Phase 3: Flow Consistency

For each flow in .agents/flows.md:

1. Verify directory exists: .agents/specs/{flow_id}/
2. Verify required files: spec.md, metadata.json
3. Verify Beads epic exists
4. Check task count matches spec

---

Phase 4: Spec Integrity

For each spec.md:

• Task IDs are sequential
• Status markers are valid: [ ], [~], [x], [!], [-]
• Checkpoint SHAs exist in git history

---

Phase 5: Git Notes

Verify git notes exist for completed tasks.

---

Phase 6: Report

Flow Validation Report

=== Structure ===
[x] .agents/ directory complete
[x] Beads initialized

=== Flows ===
[x] auth: 12 tasks, 5 complete
[!] dark-mode: Missing spec.md

=== Issues Found ===
1. dark-mode: Missing spec.md
2. auth: Task 3 marked complete but no commit SHA

=== Recommendations ===
- Run with --fix to auto-repair issues
- Manually review dark-mode

---

Phase 7: Auto-Fix (if --fix)

If --fix argument provided:

• Create missing files from templates
• Sync Beads task counts
• Add missing index files

---

Critical Rules

1. NON-DESTRUCTIVE - Only report by default
2. FIX ON REQUEST - Only modify with --fix flag
3. COMPREHENSIVE - Check everything