Commands Overview
Pro Workflow provides 11 powerful slash commands for managing your AI coding workflow. Commands are available in Claude Code (with/pro-workflow: prefix) and Cursor (as shortcuts).
All Commands
/develop
Multi-phase feature development with Research > Plan > Implement > Review workflow
/doctor
Health check for your pro-workflow setup and configuration
/commit
Smart commit with quality gates and conventional message format
/wrap-up
End-of-session ritual with change audit and learning capture
/learn-rule
Capture corrections as persistent learning rules
/handoff
Generate session handoff document for continuity
/insights
Session analytics, correction trends, and productivity metrics
/replay
Surface past learnings relevant to current task
/search
Search learnings database with FTS5 full-text search
/list
List all stored learnings from the database
/parallel
Set up parallel worktrees for zero dead time
Command Categories
Development Workflow
Core development commands for building features:/develop— Multi-phase feature builder (Research > Plan > Implement > Review)/commit— Smart commit with quality gates/doctor— Setup health check and diagnostics
Session Management
Commands for managing session state:/wrap-up— End-of-session checklist and audit/handoff— Generate handoff document for next session/parallel— Set up parallel worktrees
Learning System
Commands for the self-correction loop:/learn-rule— Capture correction as persistent rule/replay— Surface relevant past learnings/search— Full-text search of learnings/list— List all learnings/insights— Analytics and correction heatmaps
Usage in Different Tools
- Claude Code
- Cursor
Commands use the plugin namespace:After plugin install, short forms also work:
Command Patterns
Commands That Delegate to Agents
Some commands spawn specialized agents:/develop→ Spawnsorchestratoragent for multi-phase workflow- Complex commands use agent delegation for constrained execution
Commands With Arguments
Commands With Options
Quick Reference
| Command | When to Use | Output |
|---|---|---|
/develop | Building a feature | Structured workflow with phases |
/doctor | Checking setup | Health report with fixes |
/commit | Committing changes | Quality-checked commit |
/wrap-up | Ending session | Session summary + learnings |
/learn-rule | After correction | Learning saved to database |
/handoff | Ending session | Handoff document |
/insights | Reviewing progress | Analytics and trends |
/replay | Starting task | Relevant past learnings |
/search | Finding learnings | Search results with ranking |
/list | Browsing learnings | All learnings listed |
/parallel | Need parallel work | Worktree setup guide |
Best Practices
Start every session with /replay
Start every session with /replay
Before diving into a task, run
/replay <task> to surface relevant learnings from past sessions. This primes Claude with context about similar work.Use /develop for multi-file features
Use /develop for multi-file features
For features touching 3+ files, use
/develop instead of implementing directly. The research phase catches edge cases before you write code.Always /wrap-up before ending
Always /wrap-up before ending
The wrap-up ritual captures learnings and ensures clean git state. Make it habitual.
Run /doctor weekly
Run /doctor weekly
Check your setup health weekly. Catch config drift, MCP bloat, and context issues early.
Use /learn-rule after every correction
Use /learn-rule after every correction
When you correct Claude, immediately run
/learn-rule to capture the pattern. This compounds over time.Integration with Hooks
Commands integrate with the hook system:- PreToolUse hooks can suggest commands (e.g., remind about
/commitbefore git push) - PostToolUse hooks can trigger commands (e.g., run
/learn-ruleafter repeated corrections) - SessionEnd hooks can auto-run
/wrap-up
Next Steps
Try /develop
Build your first feature with the multi-phase workflow
Command API
Learn how to create custom commands