Provides intelligent context-aware PM workflow guidance with automatic phase detection. Prioritizes 6 natural workflow commands (plan, work, sync, commit, verify, done) for streamlined project management. Auto-activates when user mentions planning, implementation, verification, spec management, or asks "what command should I use". Detects workflow phase and suggests optimal command path. Provides learning mode for new users. Prevents common mistakes and offers error prevention. Works with pm-workflow state machine (IDEA → PLANNED → IMPLEMENTING → VERIFYING → VERIFIED → COMPLETE).
Detects your workflow phase and suggests the 6 natural commands (plan, work, sync, commit, verify, done) for streamlined project management. Auto-activates when you mention planning, implementation, verification, or ask "what command should I use".
/plugin marketplace add duongdev/ccpm/plugin install ccpm@duongdev-ccpm-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill helps you navigate CCPM's 49+ commands by automatically detecting your current workflow phase and suggesting the most appropriate commands.
Start here! CCPM provides 6 simple, chainable commands that cover the complete workflow:
Planning → /ccpm:plan "title" Create & plan a new task
Working → /ccpm:work Start/resume implementation
Progressing → /ccpm:sync "summary" Save progress to Linear
Committing → /ccpm:commit Create git commit (conventional)
Verifying → /ccpm:verify Run quality checks
Finalizing → /ccpm:done Create PR & finalize
Example 1: New feature from scratch
/ccpm:plan "Add two-factor authentication" my-app
/ccpm:work # Start implementation
/ccpm:sync "Implemented authenticator logic"
/ccpm:commit # Auto-formats: feat(auth): implement 2FA
/ccpm:verify # Run tests, linting, build
/ccpm:done # Create PR and finalize
Example 2: Fixing a bug
/ccpm:plan BUG-456 # Plan existing bug ticket
/ccpm:work # Resume where you left off
/ccpm:sync "Fixed race condition"
/ccpm:commit # Auto-formats: fix(cache): prevent race condition
/ccpm:verify # Ensure fix doesn't break tests
/ccpm:done # Ship the fix
Example 3: Documentation update
/ccpm:plan "Update API documentation" my-app
/ccpm:work
/ccpm:sync "Added deployment guide"
/ccpm:commit # Auto-formats: docs(api): add deployment guide
/ccpm:verify
/ccpm:done
/ccpm:plan - Smart planning
/ccpm:plan "title" <project>/ccpm:plan <issue-id>/ccpm:plan <issue-id> "changes"/ccpm:work - Smart work
/ccpm:sync - Save progress
/ccpm:commit - Git integration
fix(auth): handle token expiration/ccpm:verify - Quality checks
/ccpm:done - Finalize
The 6 natural commands cover 90% of workflows. Use project configuration commands for:
/ccpm:project:add (add new project)/ccpm:project:list, /ccpm:project:show (view projects)/ccpm:project:set (switch active project)/ccpm:figma-refresh (refresh Figma design cache)This skill activates when user mentions workflow-related keywords and provides context-aware command suggestions.
Trigger phrases:
Recommended commands:
Natural command → /ccpm:plan "Task title" <project>
Plan existing issue → /ccpm:plan <issue-id>
Update existing plan → /ccpm:plan <issue-id> "changes"
Example conversation:
User: "I need to plan the new user authentication feature"
Claude: [pm-workflow-guide activates]
I'll help you plan this. Here's what to use:
1. NEW TASK → /ccpm:plan "User authentication" my-app
2. EXISTING ISSUE → /ccpm:plan <issue-id>
3. QUICK INTERNAL → /ccpm:plan "task" my-app
The first option is recommended - it's simple and chainable!
Which applies to your situation?
Trigger phrases:
Recommended commands:
Plan the work → /ccpm:plan "Task title" <project>
Update plan with details → /ccpm:plan <issue-id> "additional requirements"
Example conversation:
User: "Let's implement the payment gateway integration"
Claude: [pm-workflow-guide activates]
⚠️ This sounds like a complex feature that needs planning first.
Recommended workflow:
1. /ccpm:plan "Payment Gateway Integration" my-app
2. Review the plan (architecture, security, API design)
3. Update plan if needed: /ccpm:plan <issue-id> "additional details"
4. Then start implementation: /ccpm:work
Would you like to start with planning?
Trigger phrases:
Recommended commands:
Natural command → /ccpm:work
Save progress → /ccpm:sync "summary"
Commit code → /ccpm:commit
feat(auth): add 2FA supportExample conversation:
User: "Let's start working on AUTH-123"
Claude: [pm-workflow-guide activates]
Perfect! Use the natural workflow:
/ccpm:work # Start implementation (auto-detects AUTH-123)
/ccpm:sync "progress note" # Save progress as you work
/ccpm:commit # Create conventional commits
/ccpm:verify # Check quality when done
/ccpm:done # Create PR and finalize
Start with: /ccpm:work
Ready to proceed?
Trigger phrases:
Recommended commands:
/ccpm:verify
Example conversation:
User: "I'm done implementing, ready to test"
Claude: [pm-workflow-guide activates]
Perfect! Let's verify your work:
/ccpm:verify
This will:
✓ Run all automated checks (tests, linting, build)
✓ Perform comprehensive code review
✓ Security audit
✓ Performance check
✓ Final approval when passing
Ready to proceed?
Trigger phrases:
Recommended commands:
/ccpm:done
Example conversation:
User: "Everything looks good, ready to ship!"
Claude: [pm-workflow-guide + external-system-safety activate]
Perfect! Let's finalize:
/ccpm:done
This will:
1. Create BitBucket PR with auto-description
2. Update Linear status to "Complete"
3. Sync Jira status to "Done"
4. Send Slack notification to team
⚠️ Note: External system writes require your confirmation
Ready to proceed?
When user asks "what's the status" → /ccpm:work <linear-issue-id>
When user asks "load this task" → /ccpm:work <linear-issue-id>
When user asks "what's available" → /ccpm:work
When user asks "how complex" → /ccpm:work <linear-issue-id>
When user asks "what depends on what" → /ccpm:work <linear-issue-id>
When user asks "show progress" → /ccpm:sync <project>
When user asks "search tasks" → /ccpm:work <project> "<query>"
When user is stuck → /ccpm:work [issue-id]
┌─────────────┐
│ IDEA │ "I need to..."
└──────┬──────┘
│ /ccpm:plan (for epics/features)
│ /ccpm:plan (for tasks)
▼
┌─────────────┐
│ PLANNED │ "Plan is ready"
└──────┬──────┘
│ /ccpm:work
▼
┌─────────────┐
│IMPLEMENTING │ "Working on it"
└──────┬──────┘
│ /ccpm:verify
▼
┌─────────────┐
│ VERIFYING │ "Testing & reviewing"
└──────┬──────┘
│ /ccpm:verify
▼
┌─────────────┐
│ VERIFIED │ "All checks passed"
└──────┬──────┘
│ /ccpm:done
▼
┌─────────────┐
│ COMPLETE │ "Shipped! 🚀"
└─────────────┘
Trigger phrases:
Command: /ccpm:repeat:check-pr <pr-number-or-url>
Trigger phrases:
Commands:
/ccpm:plan <issue-id> - Generate multiple design options/ccpm:plan <issue-id> <option-number> "<feedback>" - Iterate on design/ccpm:plan <issue-id> <option-number> - Finalize and generate specsIf user mentions issue ID directly:
User: "What's the status of AUTH-123?"
Claude: Let me check: /ccpm:work AUTH-123
If user seems lost:
User: "I don't know what to do next with this task"
Claude: Let me help: /ccpm:work <issue-id>
If user mentions external ticket:
User: "I need to plan JIRA-456"
Claude: I'll create a Linear issue and plan it: /ccpm:plan
If user asks about agents:
User: "What agents can help with backend work?"
Claude: Let me show you: /ccpm:work
This skill works alongside:
external-system-safety: Reminds user about confirmation requirements
Claude: Note: /ccpm:done will require confirmation for:
- Jira status update
- Slack notification
spec-first-development: Encourages spec creation before implementation
Claude: Before using /ccpm:work, consider:
- Does this task have a spec?
- For complex features, use /ccpm:plan first
tdd-practices: Reminds about TDD workflow
Claude: Remember: Write tests first!
The tdd-enforcer hook will block production code without tests.
Prevent common mistakes:
❌ User: "/ccpm:plan without JIRA ticket" ✅ Claude: "You'll need a Jira ticket ID. Do you have one, or should we use /ccpm:plan?"
❌ User: "/ccpm:work without planning" ✅ Claude: "I don't see a plan for this issue yet. Run /ccpm:plan first."
❌ User: "/ccpm:done before verification" ✅ Claude: "Run /ccpm:verify first to ensure quality checks pass."
This skill activates with high priority when users ask about the natural workflow:
Planning triggers:
Implementation triggers:
Verification triggers:
Completion triggers:
When these triggers appear, recommend the natural 6-command workflow first.
For new users, provide extra context:
User: "How do I plan a task?"
Claude: [pm-workflow-guide activates - detects new user]
CCPM has a simple 6-command workflow:
1. /ccpm:plan "task title" <project> - Create & plan
2. /ccpm:work - Start coding
3. /ccpm:sync "summary" - Save progress
4. /ccpm:commit - Git commit
5. /ccpm:verify - Quality checks
6. /ccpm:done - Create PR
These commands are chainable and auto-detect your issue from git branch!
For more control, extended commands like /ccpm:plan also available.
Which matches your situation?
(Tip: For complex features, consider /ccpm:plan first)
User: "I need to implement a new export feature for reports"
Claude: [pm-workflow-guide + spec-first-development activate]
Perfect! Let's use the natural workflow:
/ccpm:plan "Export reports feature" my-app
This will:
✓ Create Linear issue
✓ Gather context from Jira/Slack/Confluence
✓ Analyze codebase
✓ Generate comprehensive plan
Then continue with:
/ccpm:work # Start coding
/ccpm:sync "notes" # Save progress
/ccpm:commit # Git commit
/ccpm:verify # Quality checks
/ccpm:done # Create PR & ship
For complex features, add /ccpm:plan before /ccpm:work
Shall I start planning?
User: "I'm stuck on this auth task, not sure what to do next"
Claude: [pm-workflow-guide activates]
Let me help! Continue with the natural workflow:
/ccpm:sync "stuck on session management" # Save progress with note
Then I can help debug and suggest next steps.
What's your issue ID or branch name?
User: "I think I'm done, how do I finish this?"
Claude: [pm-workflow-guide activates]
Great! Use the natural workflow:
/ccpm:verify # Run all quality checks
Once passing, continue:
/ccpm:done # Create PR, sync Jira, ship
That's it! The natural workflow handles everything.
Ready to verify?
Full command list: /ccpm:work
Visual workflow: /ccpm:work
Search commands: Ask "what command should I use for..."
This skill helps you:
/ccpm:plan "title" <project> → Create and plan a task
/ccpm:work → Start or resume coding
/ccpm:sync "summary" → Save progress
/ccpm:commit → Create conventional git commit
/ccpm:verify → Run quality checks
/ccpm:done → Create PR and finalize
That's it! These 6 commands cover 90% of all CCPM workflows. The skill activates automatically when you mention planning, implementation, verification, or completion—providing intelligent suggestions based on your exact context.
For advanced workflows (specs, UI design, multi-agent projects), extended commands are always available.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.