Documentation Index Fetch the complete documentation index at: https://mintlify.com/gsd-build/get-shit-done/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The progress command checks project progress, summarizes recent work and upcoming tasks, then intelligently routes you to the next actionβeither executing an existing plan or creating the next one. It provides situational awareness before continuing work.
How It Works
Loads project state from STATE.md and ROADMAP.md
Analyzes recent work - Last completed phases, quick tasks, commits
Checks current position - Active phase, checkpoints, incomplete plans
Evaluates next steps - What work is ready or needed
Routes intelligently - Executes plan, creates plan, or offers options
Preserves routing logic - Implements Routes A-F from workflow
Routing Logic
The progress command uses six intelligent routing paths:
Route A: Execute Existing Plan
Condition: Phase has PLAN.md but no SUMMARY.md
β Plan exists and ready
β /gsd:execute {N}
Route B: Resume from Checkpoint
Condition: .continue-here.md exists
β Checkpoint detected
β Resume from saved state
Route C: Plan Next Phase
Condition: Current phase complete, next phase in roadmap
β Phase N complete, Phase N+1 in roadmap
β /gsd:plan-phase
Route D: Create Next Milestone
Condition: All roadmap phases complete
β Milestone complete
β /gsd:plan-milestone
Route E: Offer Options
Condition: Ambiguous state or multiple valid paths
? Multiple options available
β Present user with choices
Route F: Project Complete
Condition: All work done, no todos, clean state
β Project complete
β Celebrate and suggest next project
Usage Examples
Mid-project with ready plan
Output:
π Project Progress: E-commerce Platform
ββββββββββββββββββββββββββββββββββββββββ
**Overall Status**
β
Completed: 4/12 phases (33%)
π― Current: Phase 5 - Shopping Cart
π
Started: 2 weeks ago
**Recent Work**
β Phase 4: Product Catalog (completed 2 days ago)
- Search and filtering
- Category navigation
- Image optimization
Commit: feat: complete product catalog with search (a1b2c3d)
β Quick task: Add loading states (completed yesterday)
Commit: feat: add loading spinners to product pages (d4e5f6g)
**Current Phase: Shopping Cart**
π Status: Planned, ready to execute
π PLAN.md created: 2 days ago
β All prerequisites met
**Next Action**
Route A: Execute existing plan
Ready to implement Phase 5. Run:
/gsd:execute 5
Estimated: 3-4 hours based on plan scope
Phase complete, plan next
Output:
π Project Progress: Task Management API
βββββββββββββββββββββββββββββββββββββββ
**Overall Status**
β
Completed: 6/8 phases (75%)
π― Current: Milestone 2 (75% complete)
π
Started: 3 weeks ago
**Recent Work**
β Phase 6: Notification System (completed 1 hour ago)
- Email notifications
- Push notification service
- Notification preferences
- Event-driven architecture
Commit: feat: complete notification system (g7h8i9j)
Verified: All tests passing β
**Upcoming Work**
Next in roadmap:
- Phase 7: Real-time Updates (websockets)
- Phase 8: Performance Optimization
**Next Action**
Route C: Plan next phase
Phase 6 complete! Plan Phase 7:
/gsd:plan-phase
Or review context first:
/gsd:discuss
Resume from checkpoint
Output:
π Project Progress: Analytics Dashboard
ββββββββββββββββββββββββββββββββββββββββ
**Overall Status**
β
Completed: 2/10 phases (20%)
π― Current: Phase 3 - Data Visualization
π
Started: 1 week ago
**Recent Work**
β Phase 2: Database Schema (completed 3 days ago)
**Current Phase: Data Visualization**
βΈοΈ Status: Paused mid-execution
π Checkpoint: .continue-here.md (created 2 days ago)
π Progress: 60% complete
**Checkpoint Details**
Position: Finishing chart components
Completed:
- Line and bar charts
- Data aggregation logic
- Chart configuration
Remaining:
- Pie and scatter charts
- Interactive tooltips
- Export functionality
Blockers: None
**Next Action**
Route B: Resume from checkpoint
Continue where you left off:
/gsd:resume-work
Or start fresh:
/gsd:execute 3
Multiple options available
Output:
π Project Progress: Mobile App
βββββββββββββββββββββββββββββββ
**Overall Status**
β
Completed: 5/8 phases (62%)
π Pending todos: 4
π― Current: Between phases
**Recent Work**
β Phase 5: User Settings (completed 1 day ago)
β Quick task: Fix navigation bug (completed today)
**Available Options**
Route E: Multiple paths available
1. π Plan Phase 6: Push Notifications
Next in roadmap, prerequisites met
β /gsd:plan-phase
2. β
Work on todos (4 pending)
- High priority: Add offline support (api)
- High priority: Fix image caching (performance)
- Medium priority: Add haptic feedback (frontend)
- Low priority: Update documentation (docs)
β /gsd:check-todos
3. π Review debug sessions (1 active)
- Intermittent crash on profile page
- Status: hypothesis formed
β /gsd:debug
4. π¬ Discuss next milestone
Milestone 1 is 62% complete
β /gsd:discuss
What would you like to do?
Project complete
Output:
π Project Progress: Blog Platform
ββββββββββββββββββββββββββββββββββ
**Overall Status**
β
Completed: 8/8 phases (100%)
β
All milestones complete
β
No pending todos
β
No active debug sessions
π
Duration: 6 weeks
**Recent Work**
β Phase 8: Deployment & Monitoring (completed today)
- CI/CD pipeline
- Production deployment
- Error monitoring
- Performance tracking
Commit: feat: complete deployment and monitoring (x1y2z3a)
**Project Summary**
Milestone 1: Core Features
- β User authentication
- β Post creation and editing
- β Comment system
- β Search functionality
Milestone 2: Enhancement
- β Image upload and optimization
- β Draft management
- β SEO optimization
- β Analytics integration
**Next Action**
Route F: Project complete! π
All planned work finished. Consider:
1. π Deploy and launch
β Review deployment checklist
2. π Post-launch monitoring
β /gsd:add-todo Post-launch tasks
3. π Plan next iteration
β /gsd:new-project (new milestone)
4. π Document learnings
β Update CONTEXT.md with insights
Congratulations on completing Blog Platform!
What Gets Analyzed
Project Metrics
Total phases vs completed
Milestone progress
Project start date and duration
Commit frequency
Recent Activity
Last 3 completed phases
Last 5 quick tasks
Recent commits with messages
Last discussion or planning session
Current State
Active phase identification
Checkpoint detection
Incomplete plans (PLAN without SUMMARY)
Health issues (via implicit health check)
Upcoming Work
Next phase in roadmap
Pending todos count by area
Active debug sessions
Blockers or dependencies
Edge Case Handling
No STATE.md
No project state found.
Initialize project:
/gsd:new-project
Or resume existing project:
/gsd:resume-work
Corrupted STATE.md
State file corrupted. Running health check...
[Attempts repair]
If repair fails:
/gsd:health --repair
Ambiguous next phase
Multiple incomplete phases detected:
- Phase 4: Has PLAN, no SUMMARY
- Phase 6: Has PLAN, no SUMMARY
Which phase to execute?
Integration with Other Commands
Before planning
# Check progress first
/gsd:progress
# Then plan based on what's needed
/gsd:plan-phase
After resuming
# Resume loads basic state
/gsd:resume-work
# Progress gives detailed status
/gsd:progress
During active work
# Quick status check
/gsd:progress
# Continue working
[Returns to phase execution]
Files Read
.planning/STATE.md - Project state
.planning/ROADMAP.md - Phase definitions
.planning/CONTEXT.md - Decisions and context
.planning/phases/**/PLAN.md - Phase plans
.planning/phases/**/SUMMARY.md - Completion records
.planning/phases/**/.continue-here.md - Checkpoints
.planning/quick/*.md - Quick tasks
.planning/todos/**/*.md - Pending todos
.planning/debug/*.md - Debug sessions
.git/logs/HEAD - Recent commits
When to Use
Perfect for
Starting your work session
After completing a phase
When unsure what to do next
Before planning sessions
After long breaks
Sprint planning
Status check-ins
Pairs well with
/gsd:resume-work β /gsd:progress (detailed status)
/gsd:progress β /gsd:execute (ready to work)
/gsd:progress β /gsd:plan-phase (plan next)
/gsd:progress β /gsd:check-todos (review todos)
Success Criteria
β
Project state loaded
β
Recent work summarized
β
Current position identified
β
Next steps evaluated
β
Intelligent routing applied (Routes A-F)
β
User knows exactly what to do next