Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.
Verify plan consistency, generate summaries, and maintain plan health. This skill combines read-only inspection (verify, review) with maintenance operations (summarize, compact, rollback).
Activate when the user wants verification:
Read-Only Inspection: This Skill observes and reports, never modifies.
What We Check:
: , , (read-only tools only)
ReadGrepGlobCheck: Do status markers reflect actual state?
How to verify:
# Find all IN PROGRESS items
grep -r "🚧 IN PROGRESS" .flow/
# Find all COMPLETE items
grep -r "✅ COMPLETE" .flow/
# Find all PENDING items
grep -r "⏳ PENDING" .flow/
Common issues:
Example problem:
### 🚧 Iteration 2: Error Handling
**Status**: ✅ COMPLETE (2025-10-30) ← MISMATCH!
Report:
❌ Status Marker Mismatch
- Iteration 2 header shows 🚧 IN PROGRESS
- Implementation section shows ✅ COMPLETE
- Action: Update header to match implementation status
Check: Does every task listed in DASHBOARD.md have a corresponding file?
How to verify:
# List all tasks mentioned in DASHBOARD
grep "Task [0-9]" .flow/DASHBOARD.md
# Check if task files exist
ls .flow/phase-*/task-*.md
Common issues:
.flow/phase-2/task-5.md doesn't existExample problem:
DASHBOARD.md:
- 🚧 **Task 3**: API Integration (2/4 iterations)
But: .flow/phase-2/task-3.md doesn't exist
Report:
❌ Phantom Task Detected
- DASHBOARD.md references Task 3: API Integration
- File .flow/phase-2/task-3.md does not exist
- Action: Create task file or remove from DASHBOARD
Check: Is implementation starting before brainstorming is complete?
How to verify:
# Check if iteration has brainstorming
grep -A 20 "## Brainstorming" task-file.md
# Check brainstorming status
grep "Brainstorming.*Status.*COMPLETE" task-file.md
# Check if implementation started
grep "## Implementation" task-file.md
Gate Rule: If iteration has brainstorming, it must be ✅ COMPLETE before implementation starts.
Example problem:
## Brainstorming
**Status**: 🚧 IN PROGRESS
## Implementation
**Status**: 🚧 IN PROGRESS ← GATE VIOLATION!
Report:
❌ Implementation Gate Violation
- Iteration 2 has brainstorming IN PROGRESS
- Implementation section already started
- Action: Complete brainstorming before implementing
Check: Does task follow the Golden Rule (Standalone XOR Iterations)?
Golden Rule: Tasks have EITHER:
How to verify:
# Check if task has direct action items
grep -A 5 "## Action Items" task-file.md
# Check if task has iterations
grep "### " task-file.md | grep "Iteration"
Example problem:
# Task 3: API Integration
## Action Items
- [ ] Create StripeClient
- [ ] Add error handling
## Iterations
### Iteration 1: Setup
...
Report:
❌ Task Structure Violation (Golden Rule)
- Task 3 has both direct action items AND iterations
- Golden Rule: Tasks must be EITHER standalone OR have iterations, never both
- Action: Move action items into iterations or remove iterations
Check: Are all action items checked off when iteration is marked complete?
How to verify:
# Find iteration marked COMPLETE
grep -B 2 "Status.*COMPLETE" task-file.md
# Check for unchecked action items in that iteration
grep -A 30 "### ✅ Iteration" task-file.md | grep "\[ \]"
Example problem:
### ✅ Iteration 2: Error Handling
**Status**: ✅ COMPLETE
#### Action Items
- [x] Create ErrorMapper
- [ ] Add tests ← UNCHECKED!
- [x] Integrate with client
Report:
❌ Incomplete Action Items
- Iteration 2 marked ✅ COMPLETE
- But action item "Add tests" is unchecked
- Action: Either complete the item or mark iteration as IN PROGRESS
Check: Do all file references point to existing files?
How to verify:
# Find file references in task files
grep -r "\`.*\.ts\`" .flow/ | grep -v "example"
# Check if referenced files exist
ls path/to/file.ts
Example problem:
**Files Modified**:
- src/payment/StripeClient.ts
- src/payment/DoesNotExist.ts ← FILE DOESN'T EXIST!
Report:
⚠️ Invalid File Reference
- Iteration 2 references src/payment/DoesNotExist.ts
- File does not exist in repository
- Action: Verify file path or remove invalid reference
Task/Iteration Status:
COMPLETE - Work finished and verifiedIN PROGRESS - Currently working on thisPENDING - Not started yetREADY - Ready to implement (brainstorming complete)CANCELLED - Work abandonedDEFERRED - Moved to future versionPhase Status:
COMPLETE - All tasks in phase doneIN PROGRESS - Currently working in this phasePENDING - Phase not startedIteration Lifecycle:
⏳ PENDING
↓ (brainstorming started)
🚧 IN PROGRESS (brainstorming)
↓ (brainstorming complete, ready to implement)
🎨 READY
↓ (/flow-implement-start)
🚧 IN PROGRESS (implementing)
↓ (/flow-implement-complete)
✅ COMPLETE
Common Mistakes:
When: User asks "review the entire plan"
Steps:
Output format:
## Plan Review Results
**Summary**: 15 items checked, 2 issues found
### ✅ Passing Checks (13)
- All phase statuses consistent
- No phantom tasks detected
- Task structure valid
- ...
### ❌ Issues Found (2)
#### Issue 1: Status Marker Mismatch
- **Location**: Phase 2, Task 3, Iteration 2
- **Problem**: Header shows 🚧 but implementation shows ✅
- **Action**: Update header to ✅ COMPLETE
#### Issue 2: Unchecked Action Items
- **Location**: Phase 2, Task 4, Iteration 1
- **Problem**: Iteration marked complete but 1 action item unchecked
- **Action**: Complete action item or mark iteration IN PROGRESS
When: User asks "review Task 3"
Steps:
When: User asks "check all status markers"
Steps:
# List tasks from DASHBOARD
grep -E "Task [0-9]" .flow/DASHBOARD.md
# List actual task files
ls .flow/phase-*/task-*.md
# Compare (manual check)
# Find all IN PROGRESS items
grep -r "🚧 IN PROGRESS" .flow/
# Find unchecked action items
grep -r "\[ \]" .flow/phase-*/*.md
# Find iterations with brainstorming
grep -r "## Brainstorming" .flow/phase-*/
# Check if brainstorming is complete
grep -A 2 "## Brainstorming" .flow/phase-*/*.md | grep "Status"
# Check for direct action items in tasks
grep -A 5 "## Action Items" .flow/phase-*/task-*.md
# Check for iterations
grep "### " .flow/phase-*/task-*.md | grep -i iteration
Command: /flow-summarize
Purpose: Generate comprehensive summary of project status
# Project Summary
**Generated**: [DATE]
**Project**: [PROJECT_NAME from PLAN.md]
**Version**: [VERSION from PLAN.md]
## Overview
**Goal**: [Project goal from PLAN.md]
**Status**: [Overall status - % complete]
**Current Work**: Phase [N], Task [M], Iteration [K]
## Phase Progress
### Phase 1: [Name] ✅ COMPLETE
**Duration**: [Start date] - [End date]
**Goal**: [Phase goal]
**Completed Tasks**: [X/X]
Key deliverables:
- [Task 1: Name] - [Brief outcome]
- [Task 2: Name] - [Brief outcome]
### Phase 2: [Name] 🚧 IN PROGRESS
**Duration**: [Start date] - present
**Goal**: [Phase goal]
**Completed Tasks**: [X/Y]
Completed:
- [Task 1: Name] - [Brief outcome]
In Progress:
- [Task 2: Name] - [Current iteration]
Pending:
- [Task 3: Name] - [Purpose]
## Key Decisions
[Extract from PLAN.md Key Decisions section]
## Next Steps
1. [Immediate next action]
2. [Upcoming milestone]
3. [Blockers if any]
Command: /flow-compact
Purpose: Remove clutter from old completed work
When to Compact:
What Gets Compacted:
What's Preserved:
Process:
.flow/.backups/Command: /flow-rollback
Purpose: Undo last change if something went wrong
When to Rollback:
Rollback Process:
.flow/.backups/Backup Strategy:
Planning Stage (flow-planner Skill):
Implementation Stage (flow-builder Skill):
Design Stage (flow-designer Skill):
Verify Stage (This Skill):
Use this structure for review findings:
## Review Results
**Scope**: [What was reviewed]
**Date**: [Review date]
**Status**: [✅ All Clear | ⚠️ Issues Found]
### Summary
- X checks performed
- Y issues found
- Z warnings
### ✅ Passing Checks
- [List what's working correctly]
### ❌ Issues Found
- [List problems discovered]
### ⚠️ Warnings
- [List potential concerns]
### 📋 Recommendations
- [Suggested actions to fix issues]
❌ Critical: Must fix before proceeding
⚠️ Warning: Should fix soon
ℹ️ Info: Nice to fix
User: "Review the entire plan"
AI Process:
1. Read DASHBOARD.md to understand structure (3 phases, 8 tasks total)
2. Check each phase for status consistency
3. Verify all task files exist
4. Check task structure (standalone XOR iterations)
5. Verify status markers match implementation
6. Check action item completion
AI Response:
"## Plan Review Results
**Summary**: 15 checks performed, 2 issues found
### ✅ Passing Checks (13)
- All phase statuses consistent with task statuses
- No phantom tasks detected (all DASHBOARD tasks have files)
- Task structure valid (no mixing of action items and iterations)
- All completed iterations have checked action items
- File references valid
### ❌ Issues Found (2)
#### Issue 1: Status Marker Mismatch
- **Location**: Phase 2, Task 3, Iteration 2
- **Problem**: Header shows 🚧 IN PROGRESS but status line shows ✅ COMPLETE (2025-10-30)
- **Severity**: ⚠️ Warning (cosmetic issue)
- **Action**: Update header to `### ✅ Iteration 2: Error Handling`
#### Issue 2: Implementation Gate Violation
- **Location**: Phase 2, Task 4, Iteration 1
- **Problem**: Brainstorming status is 🚧 IN PROGRESS but Implementation section exists
- **Severity**: ❌ Critical (violates gate rule)
- **Action**: Complete brainstorming before continuing implementation"
User: "Summarize the project status"
AI Process:
1. Read DASHBOARD.md for current work and progress
2. Read PLAN.md for project context
3. Read all task files for completion details
4. Generate formatted summary
AI Response:
"# Project Summary
**Generated**: 2025-11-02
**Project**: Flow Framework Agent Skills
**Version**: 1.0.0
## Overview
**Goal**: Refactor 8 workflow stage-based agent skills from 28 slash commands
**Status**: 57% complete (4/7 iterations in current task)
**Current Work**: Phase 3, Task 4, Iteration 5
## Phase Progress
### Phase 1: Foundation ✅ COMPLETE
**Duration**: Oct 15 - Oct 22
**Goal**: Set up project structure
**Completed Tasks**: 2/2
Key deliverables:
- Task 1: Project Setup - Framework structure established
- Task 2: Documentation - Architecture spec complete
### Phase 2: Initial Skills 🚧 IN PROGRESS
**Duration**: Oct 23 - present
**Goal**: Build core workflow skills
**Completed Tasks**: 2/4
Completed:
- Task 1: flow-initializer - Project initialization complete
- Task 2: flow-planner - Planning workflows done
In Progress:
- Task 4: Stage-Based Skills - Building flow-designer + flow-builder (Iteration 5 of 7)
Pending:
- Task 5: Verification Skills - Not started
## Key Decisions
- Progressive disclosure strategy: SKILL.md (400-500 lines) + supporting files
- 8 workflow stage-based skills absorb all 28 commands
- Dashboard-first navigation pattern throughout
## Next Steps
1. Complete Iteration 5 (flow-completer + flow-navigator)
2. Begin Iteration 6 (flow-verifier + flow-curator)
3. Final verification and integration testing"
User: "The DASHBOARD is getting too long, can you clean it up?"
AI Process:
1. Read DASHBOARD.md (780 lines)
2. Identify completed items older than 30 days (Phase 1 completed Oct 22)
3. Create backup before compacting
AI Response:
"I'll compact old completed work to reduce clutter.
**Before Compacting**:
- Created backup: .flow/.backups/2025-11-02-143022-pre-compact.zip
- Current DASHBOARD.md: 780 lines
- Identified items to compact: Phase 1 (completed 11 days ago)
**What Will Be Compacted**:
- Phase 1, Task 1: Remove 45 lines of implementation notes (keep summary)
- Phase 1, Task 2: Remove 38 lines of detailed action items (keep count)
- Preserve all status markers and completion dates
**After Compacting**:
- New DASHBOARD.md: ~520 lines (33% reduction)
- All important info preserved
- Backup available for rollback if needed
Proceed with compact operation?"
User: "Oh no, I accidentally deleted important content. Can you undo that?"
AI Process:
1. List backups in .flow/.backups/
2. Show recent backups with timestamps
AI Response:
"Available backups:
1. 2025-11-02 14:30:22 - Pre-compact (DASHBOARD.md, 780 lines)
2. 2025-11-01 16:45:10 - Pre-plan-split (3 phase files archived)
3. 2025-10-31 09:20:15 - Manual backup (full project)
Which backup would you like to restore?
User: "Restore backup 1"
AI Process:
1. Restore DASHBOARD.md from backup 1
2. Verify restored file
3. Report what was rolled back
AI Response:
"✅ Rollback complete!
**Restored**:
- .flow/DASHBOARD.md (from 2025-11-02 14:30:22 backup)
- File size: 780 lines
- All content restored to pre-compact state
**What Changed**:
- Phase 1 details restored (83 lines of implementation notes)
- Detailed action items restored
- Current file backed up to .flow/.backups/2025-11-02-145530-pre-rollback.zip (just in case)
Your content is back!"
/flow-verify-plan, /flow-summarize, /flow-compact, /flow-rollbackBefore reviewing:
During review:
After review: