Skip to main content
Pro Workflow works with Claude Code, Cursor, and 32+ AI coding agents via SkillKit. Choose the installation method that matches your environment.

Cursor Installation

1

Add Plugin

The fastest way to install in Cursor:
/add-plugin pro-workflow
This command automatically installs:
  • 11 skills - Core workflow patterns, smart-commit, wrap-up, learn-rule, context-optimizer, orchestrate, and more
  • 5 agents - planner, reviewer, scout, orchestrator, debugger
  • 6 rules - quality-gates, atomic-commits, context-discipline, self-correction, no-debug-statements, communication-style
2

Verify Installation

Check that the plugin loaded successfully:
/doctor
You should see:
Pro-Workflow Health Check
  Installation:  OK
  Rules:         6 active
  Skills:        11 loaded
  Agents:        5 available
3

Test a Skill

Try the self-correction pattern:
You: Make a deliberate mistake
AI: [makes mistake]
You: That's wrong, remember this
AI: [proposes LEARN rule for approval]
Cursor users get equivalent hook behavior through .mdc rules in the rules/ directory. All patterns work the same, just enforced via Cursor’s rule system instead of hooks.

Claude Code Installation

1

Add from Marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
All commands are now available with the /pro-workflow: prefix.
2

Build with SQLite Support

For searchable learnings with full-text search:
cd ~/.claude/plugins/*/pro-workflow
npm install && npm run build
This creates the SQLite database at ~/.pro-workflow/data.db with FTS5 indexing.
3

Test Commands

Commands work with short aliases:
/develop add authentication
/doctor
/wrap-up
/search "testing patterns"

Method 2: Load Directly

claude --plugin-dir /path/to/pro-workflow
Use this method when:
  • You want to modify the plugin locally
  • You’re developing custom commands or agents
  • You need to test changes before publishing

Command Reference

CommandAliasDescription
/pro-workflow:wrap-up/wrap-upEnd-of-session checklist
/pro-workflow:learn-rule/learn-ruleExtract correction to memory
/pro-workflow:commit/commitSmart commit with quality gates
/pro-workflow:develop/developMulti-phase feature build
/pro-workflow:doctor/doctorHealth check for setup
/pro-workflow:insights/insightsSession analytics and heatmap
/pro-workflow:replay/replaySurface past learnings
/pro-workflow:handoff/handoffGenerate session handoff
/pro-workflow:search/searchSearch learnings by keyword
/pro-workflow:list/listList all stored learnings
After plugin install, short forms like /develop work directly. No need to use the full prefix.

Manual Installation (Any Agent)

For agents without plugin support, or if you prefer manual setup:
1

Clone Repository

git clone https://github.com/rohitg00/pro-workflow.git /tmp/pw
2

Copy Templates

cp -r /tmp/pw/templates/split-claude-md/* ./.claude/
This creates a modular memory structure:
.claude/
├── CLAUDE.md        # Entry point
├── AGENTS.md        # Workflow rules
├── SOUL.md          # Style preferences
└── LEARNED.md       # Auto-populated corrections
3

Optional: Copy Commands

cp -r /tmp/pw/commands/* ~/.claude/commands/
Makes commands like /wrap-up and /develop available.

Minimal Setup

If you just want the core patterns, add this to your CLAUDE.md:
## Pro Workflow

### Self-Correction
When corrected, propose rule → add to LEARNED after approval.

### Planning
Multi-file: plan first, wait for "proceed".

### Quality
After edits: lint, typecheck, test.

### LEARNED
This gives you the self-correction loop without any dependencies.

SkillKit Installation (32+ Agents)

Use SkillKit to install Pro Workflow on any of 32+ supported agents:
1

Install Pro Workflow

npx skillkit install pro-workflow
2

Translate for Your Agent

npx skillkit translate pro-workflow --agent cursor
3

Verify

Check that skills are available in your agent:
# Agent-specific verification
# See your agent's docs for skill listing commands
SkillKit translates Pro Workflow patterns into the native format for each agent. All core patterns (self-correction, quality gates, orchestration) work the same way.

Supported Agents

Pro Workflow works across these agents via SkillKit:
  • Claude Code
  • Cursor
  • Codex CLI
  • Gemini CLI
  • Windsurf
  • 27+ more agents
See Cross-Agent Workflows for configuration mapping.

Configuration

Settings Example

Pro Workflow includes a production-ready settings template at settings.example.json:
{
  "permissions": {
    "deny": [
      "Bash(rm -rf *)",
      "Bash(curl * | bash)",
      "Edit(/node_modules/**)"
    ],
    "ask": [
      "Bash(git push *)",
      "Bash(docker *)",
      "Bash(npm publish *)"
    ],
    "allow": [
      "Read", "Glob", "Grep", "Edit", "Write",
      "Bash(git status)",
      "Bash(git diff *)",
      "MCP(github:*)",
      "Task(*)",
      "Agent(*)"
    ]
  },
  "outputStyle": "Explanatory",
  "statusLine": "model branch tokens",
  "plansDirectory": ".claude/plans",
  "env": {
    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "80"
  },
  "spinnerVerbs": ["Thinking", "Analyzing", "Exploring"]
}
Permission Rules
  • deny - Block dangerous operations (force delete, pipe to bash)
  • ask - Require approval (git push, docker, npm publish)
  • allow - Auto-approve (read operations, git status, tests)
Output Configuration
  • outputStyle - “Minimal”, “Explanatory”, or “Verbose”
  • statusLine - “model branch tokens” shows context in status
  • attribution - Commit message and PR description attribution
Context Management
  • CLAUDE_AUTOCOMPACT_PCT_OVERRIDE - Compact before 95% (default: 50-80%)
  • plansDirectory - Where to store plan files
See Settings Guide for all options.

MCP Configuration

Pro Workflow includes curated MCP recommendations at mcp-config.example.json:

context7

Live documentation lookup - essential for API references

playwright

Browser automation - most token-efficient

GitHub

PRs, issues, code search - integrate with workflows
Rule: Start with 3 MCPs. Add only for concrete needs.Each MCP adds to context consumption. Pro Workflow recommends:
  • Keep < 10 MCP servers enabled
  • Keep < 80 total tools
  • Disable unused servers via disabledMcpjsonServers in settings

Database Setup (Claude Code)

Pro Workflow stores learnings in SQLite with FTS5 full-text search:
~/.pro-workflow/
└── data.db    # SQLite database with learnings and sessions

Initialize Database

cd ~/.claude/plugins/*/pro-workflow
npm run db:init

Search Learnings

/search testing           # Find all testing-related learnings
/search "file paths"      # Exact phrase search
/list                     # List all learnings
The database automatically captures:
  • LEARNED rules from self-correction
  • Session stats (edits, corrections, quality gate runs)
  • Searchable learning index for quick retrieval

Hooks Setup (Claude Code)

Pro Workflow includes 18 hook events for automated workflow enforcement:
# Copy hooks to your settings
cp ~/skills/pro-workflow/hooks/hooks.json ~/.claude/settings.local.json

Hook Events

TriggerAction
Edit/WriteTrack edit count, remind at 5/10 edits
git commitRemind to run quality gates
git pushRemind about /wrap-up
TriggerAction
Code edit (.ts/.js/.py/.go)Check for console.log, TODOs, secrets
Test commandsSuggest [LEARN] from failures
HookAction
SessionStartLoad LEARNED patterns, show worktree count
StopContext-aware reminders
SessionEndCheck uncommitted changes, prompt for learnings
ConfigChangeDetect mid-session changes
  • SubagentStart/Stop - Log agent lifecycle
  • TaskCompleted - Quality gate on completion
  • PermissionRequest - Flag dangerous operations
  • PostToolUseFailure - Track failures, suggest learnings
  • TeammateIdle - Detect blockers in agent teams

Hook Philosophy

  • Non-blocking - Hooks remind, don’t block (except dangerous ops)
  • Checkpoint-based - Quality gates at intervals, not every edit
  • Learning-focused - Always prompt for pattern capture

Verify Installation

Run the /doctor command to check your setup:
/doctor
Pro-Workflow Health Check
  Installation:  OK
  Hooks:         ACTIVE
  Context:       15% (healthy)
  MCPs:          3 active (OK)
  CLAUDE.md:     42 lines (OK)
  Git:           clean

Troubleshooting

cp -r /path/to/pro-workflow/commands/* ~/.claude/commands/
mkdir -p ~/.pro-workflow
cd ~/.claude/plugins/*/pro-workflow
npm run build
Check that paths in hooks.json use absolute paths or ${CLAUDE_PLUGIN_ROOT}:
{
  "script": "${CLAUDE_PLUGIN_ROOT}/scripts/pre-tool-use.sh"
}
Run manual compaction:
/compact
Or configure earlier auto-compact:
{
  "env": {
    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50"
  }
}

Repository Structure

Understanding the layout helps with customization:
pro-workflow/
├── .claude-plugin/              # Claude Code plugin definition
├── .cursor-plugin/              # Cursor plugin definition
├── skills/                      # 11 skills (Cursor + Claude Code)
│   ├── pro-workflow/SKILL.md
│   ├── smart-commit/SKILL.md
│   ├── context-optimizer/SKILL.md
│   ├── orchestrate/SKILL.md
│   └── ...
├── agents/                      # 5 agents
│   ├── planner.md
│   ├── reviewer.md
│   ├── scout.md
│   ├── orchestrator.md
│   └── debugger.md
├── commands/                    # 10 slash commands
│   ├── develop.md
│   ├── doctor.md
│   ├── wrap-up.md
│   └── ...
├── hooks/                       # 18 hook events
│   └── hooks.json
├── docs/                        # 7 reference guides
│   ├── settings-guide.md
│   ├── cli-cheatsheet.md
│   ├── orchestration-patterns.md
│   └── ...
├── rules/                       # 6 Cursor rules
├── contexts/                    # 3 context modes
├── templates/                   # Split CLAUDE.md templates
├── settings.example.json        # Production settings template
├── mcp-config.example.json      # Curated MCP recommendations
└── src/                         # TypeScript source (SQLite)

Next Steps

Quickstart

Try your first command in 30 seconds

Core Patterns

Learn the patterns that make Pro Workflow powerful

Commands

Master all 10 commands and their usage

Settings Guide

Deep dive into configuration options

Build docs developers (and LLMs) love