gh-duongdev-ccpm/commands

PM Commands 2.0 - Interactive Mode

Project Management commands with Interactive Mode for seamless workflow automation across Jira, Confluence, BitBucket, Slack, and Linear.

⚡ Quick Start - Natural Workflow Commands

Learn 6 commands, master your workflow.

CCPM provides natural, verb-based commands optimized for maximum efficiency. These commands implement functionality directly (no routing overhead) and leverage session-level caching for 63-67% token reduction.

The 6-Command Workflow (Optimized in v2.3)

# 1. PLAN - Create or update tasks (2,450 tokens, 65% reduction)
/ccpm:plan "Add user authentication"              # Create new task
/ccpm:plan WORK-123                                # Plan existing task
/ccpm:plan WORK-123 "Also add 2FA"                 # Update plan

# 2. WORK - Start or continue work (5,000 tokens, 67% reduction)
/ccpm:work WORK-123                                # Auto-detects: start or resume
/ccpm:work                                         # Auto-detects issue from branch

# 3. SYNC - Save progress (anytime) (2,100 tokens, 65% reduction)
/ccpm:sync                                         # Auto-detects issue from branch
/ccpm:sync "Completed auth endpoints"              # With custom summary

# 4. COMMIT - Git integration (2,000 tokens, already optimized)
/ccpm:commit                                       # Auto-generates conventional commit
/ccpm:commit "Finished login screen"               # Custom message (auto-formatted)

# 5. VERIFY - Quality checks + verification (2,800 tokens, 65% reduction)
/ccpm:verify                                       # Runs checks, then verification
/ccpm:verify WORK-123                              # Explicit issue ID

# 6. DONE - Finalize (PR + sync + complete) (2,100 tokens, 65% reduction)
/ccpm:done                                         # Auto-detects, creates PR, syncs

Token Budget: Complete workflow: ~16,500 tokens (vs ~44,500 before, 63% reduction)

Complete Example Workflow

# Start a new task
/ccpm:plan "Add JWT authentication" my-app

# System creates Linear issue WORK-123, plans it
# Suggests: Start work? → Yes

# Begin implementation (creates branch, loads context)
/ccpm:work WORK-123

# ... make changes, implement features ...

# Save progress periodically
/ccpm:sync "Implemented token validation"

# Commit your work (conventional commits format)
/ccpm:commit "Completed auth middleware"

# Continue working...
/ccpm:work

# ... finish all subtasks ...

# Verify quality
/ccpm:verify

# System runs linting, tests, code review
# All pass → Suggests: Finalize?

# Complete and create PR
/ccpm:done

# System creates PR, syncs to Jira, marks complete
# Total: 6 commands for complete workflow!

Key Features

✅ Smart Auto-Detection

• Issue ID from git branch name
• Mode from arguments (create vs plan vs update)
• Status to determine start vs resume

✅ Conventional Commits

• Automatic formatting
• Links to Linear issues
• Smart type detection (feat/fix/docs)

✅ Workflow State Detection

• Warns about uncommitted changes
• Detects stale syncs (>2h)
• Checks task completion
• Validates branch pushed

✅ Smart Suggestions

• Context-aware next actions
• Time-based recommendations
• Status-based routing

PSN-30 Optimizations (v2.3)

🚀 Performance Improvements:

• 63-67% token reduction across all natural commands
• Direct implementation (no routing overhead)
• Linear subagent caching with 85-95% hit rates
• Smart agent selection (automatic optimal agent choice)
• Batch operations (combine multiple API calls)
• 3-5x faster response times for cached operations

📊 Token Budget per Command:

• /ccpm:plan: 2,450 tokens (was 7,000)
• /ccpm:work: 5,000 tokens (was 15,000)
• /ccpm:sync: 2,100 tokens (was 6,000)
• /ccpm:commit: 2,000 tokens (already optimized)
• /ccpm:verify: 2,800 tokens (was 8,000)
• /ccpm:done: 2,100 tokens (was 6,000)

💰 Cost Savings:

• Complete workflow: ~16,500 tokens (vs 44,500 before)
• Annual savings: $300-$3,000 depending on usage
• Faster execution: <50ms for cached operations

For detailed metrics, see Token Savings Report

Migration from Old Commands

These commands replace (but don't break) the existing workflow:

Old Command	New Command	Benefit
/ccpm:planning:create	/ccpm:plan "title"	Natural syntax
/ccpm:planning:plan	/ccpm:plan WORK-123	Shorter
/ccpm:planning:update	/ccpm:plan WORK-123 "changes"	One command for all
/ccpm:implementation:start	/ccpm:work	Auto-detects mode
/ccpm:implementation:next	/ccpm:work	Same command
/ccpm:implementation:sync	/ccpm:sync	Auto-detects issue
(manual git)	/ccpm:commit	NEW - Built-in
/ccpm:verification:check + :verify	/ccpm:verify	Sequential flow
/ccpm:complete:finalize	/ccpm:done	Safety checks

All old commands still work - they now show hints to use the new workflow commands.

---

🚨 Critical Safety Notice

All PM commands enforce strict safety rules to prevent accidental external system modifications.

Read: SAFETY_RULES.md

• ✅ Read operations - Freely gather from Jira/Confluence/BitBucket/Slack
• ⛔ Write operations - Require explicit user confirmation (even in bypass mode)
• ✅ Linear operations - Permitted (internal tracking)

🎯 What's New in 2.0

Interactive Mode

Every command now:

• ✅ Shows current status after execution
• ✅ Calculates and displays progress
• ✅ Suggests intelligent next actions
• ✅ Asks what you want to do next
• ✅ Can chain directly to next command

No more context switching! Complete workflows in one continuous session.

New Commands (18 Total in v2.0)

Spec Management (6 new):

1. /ccpm:spec:create - Create Epic/Feature with Linear Document
2. /ccpm:spec:write - AI-assisted spec writing
3. /ccpm:spec:review - Spec validation & grading
4. /ccpm:spec:break-down - Epic→Features, Feature→Tasks
5. /ccpm:spec:migrate - Migrate .claude/ specs to Linear
6. /ccpm:spec:sync - Sync spec with implementation

Workflow Enhancements (13 new): 7. /ccpm:planning:create - Create + plan in one step 8. /ccpm:planning:update - Update existing plan with interactive clarification 9. /ccpm:utils:report - Project-wide progress reporting 10. /ccpm:utils:context - Fast task context loading 11. /ccpm:utils:search - Search tasks by text query 🔍 12. /ccpm:implementation:next - Smart next action detection 13. /ccpm:implementation:sync - Sync progress, findings & changes to Linear 14. /ccpm:complete:finalize - Post-completion workflow 15. /ccpm:utils:sync-status - Jira sync with confirmation 16. /ccpm:utils:auto-assign - AI-powered agent assignment 17. /ccpm:utils:rollback - Undo planning changes 18. /ccpm:utils:dependencies - Visualize task dependencies 19. /ccpm:utils:insights - AI complexity & risk analysis

📋 Complete Command Reference

Spec Management Commands 🆕

/ccpm:spec:create <type> "<title>" [parent-id]

Create Epic/Feature/Initiative with Linear Document for comprehensive spec management.

Types:

• epic or initiative - High-level project/feature group
• feature - Specific feature (can belong to an epic)

What it does:

• Creates Epic (Initiative) or Feature (Parent Issue) in Linear
• Creates associated Linear Document for spec/design
• Links document to issue
• Populates with appropriate template

# Create Epic with spec document
/ccpm:spec:create epic "User Authentication System"

# Create Feature under an epic
/ccpm:spec:create feature "JWT Auth" WORK-100

/ccpm:spec:write <doc-id> <section>

AI-assisted spec document writing with codebase analysis.

Sections: requirements, architecture, api-design, data-model, testing, security, user-flow, timeline, all

What it does:

• Analyzes existing codebase for patterns
• Fetches library documentation (Context7)
• Generates detailed, specific content
• Follows project conventions

# Write specific section
/ccpm:spec:write DOC-123 requirements

# Write API design with examples
/ccpm:spec:write DOC-123 api-design

# Write all sections at once
/ccpm:spec:write DOC-123 all

/ccpm:spec:review <doc-id>

AI-powered spec review for completeness and quality.

What it does:

• Analyzes completeness (required vs optional sections)
• Validates content quality (specificity, testability)
• Identifies risks and gaps
• Grades spec (A-F) with detailed feedback
• Suggests improvements

/ccpm:spec:review DOC-123

Output:

• Completeness score (0-100%)
• Quality assessment
• Risk identification
• Actionable recommendations
• Best practices checklist

/ccpm:spec:break-down <epic-or-feature-id>

Break down Epic into Features or Feature into Tasks based on spec.

What it does:

• Parses spec document for breakdown items
• Generates Features (from Epic) or Tasks (from Feature)
• Creates Linear issues with proper hierarchy
• Links back to spec
• Detects dependencies

# Break Epic into Features
/ccpm:spec:break-down WORK-100

# Break Feature into Tasks
/ccpm:spec:break-down WORK-101

Features:

• Auto-extracts from "Features Breakdown" or "Task Breakdown" sections
• AI suggests missing items
• Preserves dependencies
• Maps priorities (P0=Urgent, P1=High, etc.)
• Converts estimates to Linear points

/ccpm:spec:migrate <project-path> [category]

Migrate existing markdown specs from .claude/ to Linear Documents.

Categories: docs, plans, enhancements, tasks, all (default)

What it does:

• Scans .claude/ directory for markdown files
• Categorizes files (Epic, Feature, Task, Documentation)
• Creates Linear Issues + Documents
• Preserves content and metadata
• Moves originals to .claude/migrated/

# Migrate from current directory (most common)
/ccpm:spec:migrate .

# Migrate from specific project path
/ccpm:spec:migrate ~/personal/personal-project

# Migrate only specific category (skip selection)
/ccpm:spec:migrate . enhancements

Interactive Selection:

• Select which categories to migrate (Epics, Features, Tasks, Docs)
• Shows file counts for each category
• Can select multiple categories
• Full preview before confirming

Migration Process:

1. Discovers and categorizes all .md files
2. Shows preview with file counts
3. Asks for confirmation
4. Creates Linear entities with documents
5. Extracts checklists → sub-tasks
6. Moves originals to .claude/migrated/
7. Creates breadcrumb files with Linear links

Safe Migration:

• Original files NOT deleted (moved to .claude/migrated/)
• Full content preserved in Linear Documents
• Breadcrumb files created for reference
• Can rollback from .claude/migrated/ if needed

/ccpm:spec:sync <doc-id-or-issue-id>

Sync spec document with implementation reality.

What it does:

• Compares spec with actual implementation
• Detects drift in requirements, API, data model, tasks
• Searches codebase for implemented code
• Generates detailed drift report
• Offers to update spec or create implementation tasks

/ccpm:spec:sync DOC-123
# or
/ccpm:spec:sync WORK-123

Drift Detection:

• Requirements: Missing, extra, or changed features
• API Design: Endpoint signatures, new/missing endpoints
• Data Model: Schema changes, field modifications
• Tasks: Status mismatches between spec and Linear

Sync Options:

• Update spec to match reality (recommended)
• Update implementation to match spec
• Hybrid approach (choose per item)
• Review only

Planning Commands

/ccpm:planning:create "<title>" <project> [jira-ticket-id] 🆕

Create Linear issue + run full planning in one step.

• No manual Linear UI needed
• Automatically populates with research
• Interactive next action prompts

/ccpm:planning:create "Add JWT authentication" my-app TRAIN-456

/ccpm:planning:plan <linear-issue-id> [jira-ticket-id]

Populate existing Linear issue with comprehensive research.

• Checklist at top
• All links properly formatted
• Supports with/without Jira

/ccpm:planning:plan WORK-123 TRAIN-456

/ccpm:planning:update <linear-issue-id> "<update-request>" 🆕

Update existing plan with interactive clarification.

• Analyzes current plan and update request
• Asks smart clarifying questions
• Shows impact analysis (complexity, timeline)
• Tracks change history
• Confirms before updating

/ccpm:planning:update WORK-123 "Also add email notifications"
/ccpm:planning:update WORK-456 "Use Redis instead of in-memory cache"
/ccpm:planning:update WORK-789 "Remove admin dashboard, just add API"

What it does:

• Fetches current plan from Linear
• Detects change type (scope, approach, simplification, blocker)
• Asks targeted questions for clarification
• Gathers additional context (codebase, Context7, external PM)
• Generates updated plan with impact analysis
• Shows side-by-side comparison of changes
• Confirms before updating Linear
• Suggests next actions after update

/ccpm:planning:quick-plan "<description>" <project>

Quick planning for Personal Project (no external PM).

/ccpm:planning:quick-plan "Add dark mode" personal-project

Implementation Commands

/ccpm:implementation:start <linear-issue-id>

Start implementation with agent coordination.

• Lists available agents
• Creates assignment plan
• Begins execution

/ccpm:implementation:start WORK-123

/ccpm:implementation:next <linear-issue-id> 🆕

Smart next action detection based on status & dependencies.

• Respects task dependencies
• Suggests optimal next step
• One-click execution

/ccpm:implementation:next WORK-123

/ccpm:implementation:update <linear-issue-id> <idx> <status> "<msg>"

Update subtask progress.

/ccpm:implementation:update WORK-123 0 completed "Added auth endpoints"

/ccpm:implementation:sync <linear-issue-id> [summary] 🆕

Sync implementation progress, findings, and code changes to Linear for full context resume.

Auto-detects:

• Git changes (files modified/created/deleted)
• Code diffs and statistics
• TODO/FIXME comments
• New dependencies

Interactive prompts for:

• Technical decisions & findings
• Blockers & challenges (resolved/active)
• Test results & quality metrics

Updates Linear with:

• Detailed progress comment with all changes
• "Implementation Notes" section in description
• Automatic checklist updates
• Relevant labels (blocked, needs-review)

# Full interactive mode with git detection
/ccpm:implementation:sync WORK-123

# Quick manual sync with summary
/ccpm:implementation:sync WORK-123 "Completed auth impl, all tests passing"

# Sync with blocker
/ccpm:implementation:sync WORK-123 "Blocked: Need backend API deployed"

Use Cases:

• End of work session → Save progress before stopping
• After major milestone → Document completion
• When blocked → Record blocker for team awareness
• Before task switching → Save state before context switch
• Mid-day checkpoints → Track progress on long tasks

Benefits:

• 🎯 Capture full implementation context for easy resume
• 📊 Give team/stakeholders real-time progress visibility
• 🧠 Document technical decisions as they're made
• ⚡ Auto-detect changes from git (no manual entry)

Verification Commands

/ccpm:verification:check <linear-issue-id>

Run quality checks before verification.

• IDE warnings/errors
• Linting (auto-fix)
• Test execution
• Updates to Verification status if all pass

/ccpm:verification:check WORK-123

/ccpm:verification:verify <linear-issue-id>

Final verification with verification-agent.

• Comprehensive review
• Regression checks
• Marks as Done if passes

/ccpm:verification:verify WORK-123

/ccpm:verification:fix <linear-issue-id>

Fix verification failures with agent coordination.

• Analyzes failures
• Maps to agents
• Parallel fixes

/ccpm:verification:fix WORK-123

Completion Commands

/ccpm:complete:finalize <linear-issue-id> 🆕

Post-completion workflow with confirmations.

• Create PR (optional)
• Sync Jira status (with confirmation)
• Notify Slack (with confirmation)
• Archive and clean up

/ccpm:complete:finalize WORK-123

Utility Commands

/ccpm:utils:status <linear-issue-id>

Show detailed task status with next actions.

/ccpm:utils:status WORK-123

/ccpm:utils:context <linear-issue-id> 🆕

Load full task context for quick resume.

• Fetches issue details
• Loads relevant files
• Shows progress
• Suggests next actions

/ccpm:utils:context WORK-123

/ccpm:utils:report <project> 🆕

Project-wide progress report.

• All active tasks
• Blocked items highlighted
• Velocity metrics
• Interactive next actions

/ccpm:utils:report my-app

/ccpm:utils:insights <linear-issue-id> 🆕

AI-powered complexity & risk analysis.

• Complexity scoring (1-10)
• Risk identification
• Timeline estimation
• Optimization recommendations

/ccpm:utils:insights WORK-123

/ccpm:utils:auto-assign <linear-issue-id> 🆕

AI-powered agent assignment.

• Analyzes each subtask
• Suggests optimal agent
• Detects parallelization opportunities
• Creates execution plan

/ccpm:utils:auto-assign WORK-123

/ccpm:utils:sync-status <linear-issue-id> 🆕

Sync Linear status to Jira (with confirmation).

• Shows preview
• Asks confirmation
• Updates Jira

/ccpm:utils:sync-status WORK-123

/ccpm:utils:rollback <linear-issue-id> 🆕

Rollback planning to previous version.

• Shows history
• Preview before rollback
• Confirmation required

/ccpm:utils:rollback WORK-123

/ccpm:utils:dependencies <linear-issue-id> 🆕

Visualize subtask dependencies.

• ASCII dependency graph
• Shows ready vs blocked
• Execution order

/ccpm:utils:dependencies WORK-123

/ccpm:utils:search <project> <search-query> 🆕

Search and list tasks from a project by text query.

What it does:

• Searches issue titles and descriptions
• Filters by project
• Shows status, progress, and metadata
• Provides quick action links
• Interactive next action menu

# Search for authentication tasks
/ccpm:utils:search my-app "authentication"

# Search for UI components
/ccpm:utils:search my-project "button component"

# Search all projects (use empty string)
/ccpm:utils:search "" "Redis"

Features:

• Fast text search via Linear API
• Up to 50 results, ordered by update time
• Shows progress percentages
• Quick actions for each result
• Excludes archived by default

/ccpm:utils:agents

List all available subagents.

/ccpm:utils:agents

/ccpm:utils:help [issue-id] 🆕

Context-aware help and command suggestions.

What it does:

• Shows categorized command reference
• Suggests relevant commands based on current status
• Provides workflow guidance
• Interactive quick actions

# General help
/ccpm:utils:help

# Context-aware help with suggestions
/ccpm:utils:help WORK-123

Features:

• Detects issue status and suggests next actions
• Shows all available commands by category
• Workflow quick reference
• Interactive action menu

/ccpm:utils:cheatsheet 🆕

Visual workflow cheatsheet with decision trees and quick reference.

What it shows:

• Complete workflow diagrams (Spec-First and Task-First)
• Decision trees to find the right command
• Quick syntax reference for all commands
• Common workflow patterns
• Pro tips and best practices

/ccpm:utils:cheatsheet

Perfect for:

• New users learning CCPM
• Quick command lookup
• Understanding workflow patterns
• Finding the right command for your situation

🔄 Interactive Workflow Example

# 1. Create & Plan
/ccpm:planning:create "Add JWT auth" my-app TRAIN-456

📋 Issue Created: WORK-123
✅ Planning Complete!

💡 What would you like to do next?
  1. Start Implementation ⭐
  2. Get AI Insights
  3. Auto-Assign Agents
  4. Just Review

→ [You select: 1. Start Implementation]

# 2. Implementation Starts Automatically
📝 Assignment Plan Created
🤖 3 agents assigned

💡 Which subtask first?
  1. Auto-select (AI) ⭐
  2. Subtask 1: Database schema
  3. View All

→ [You select: 1. Auto-select]

# 3. Work Continues...
[Agent completes subtask 1]

✅ Subtask 1 Complete!
🎯 Progress: 1/5 (20%)

💡 Next action?
  1. Continue Next Task ⭐
  2. Run Quality Checks
  3. Update Status

→ [Continuous workflow...]

# 4. All Done
✅ All Subtasks Complete!

💡 Ready for quality checks?
  1. Run Checks ⭐
  2. Review First

→ [You select: 1]

# 5. Verification
✅ Quality Checks Passed!

💡 Run final verification?
  1. Verify Now ⭐
  2. Additional Tests

→ [You select: 1]

# 6. Finalize
🎉 Verification Passed!

💡 Finalize this task?
  1. Finalize (PR + Jira + Slack) ⭐
  2. Just PR
  3. Keep Open

→ [One continuous flow from start to finish!]

🎯 Best Practices

Spec-First Workflow (Recommended for Personal Project)

For new features or major projects:

1. Create Epic/Feature with Spec → /ccpm:spec:create
2. Write Comprehensive Spec → /ccpm:spec:write (all sections)
3. Review & Validate → /ccpm:spec:review
4. Break Down into Tasks → /ccpm:spec:break-down
5. Implement Tasks → /ccpm:implementation:start
6. Keep Spec in Sync → /ccpm:spec:sync (periodically)

Benefits:

• Clear requirements before coding
• Better estimates and planning
• Easier onboarding and handoffs
• Documentation-first approach
• Reduce scope creep

Task-First Workflow (For smaller tasks)

1. Start with /ccpm:planning:create - One command to create + plan
2. Use /ccpm:utils:context when resuming work
3. Run /ccpm:implementation:next when unsure what's next
4. Check /ccpm:utils:report daily for project overview
5. Get /ccpm:utils:insights early for complex tasks
6. Always /ccpm:verification:check before /ccpm:verification:verify
7. Trust interactive prompts - They know the workflow
8. Let it flow - Each command suggests the next

Migrating Existing Specs

If you have existing markdown specs in .claude/:

1. Run Migration → /ccpm:spec:migrate ~/personal/personal-project
2. Review in Linear - Check migrated items
3. Organize Hierarchy - Link features to epics
4. Continue with Spec Workflow - Use spec commands going forward

📊 Command Workflow Map

Spec-First Workflow

Create Epic/Feature (/ccpm:spec:create)
  ↓
Write Spec (/ccpm:spec:write)
  ↓
Review Spec (/ccpm:spec:review)
  ↓
Break Down (/ccpm:spec:break-down) → Creates Tasks
  ↓
[Continue with Task-First Workflow below]

Task-First Workflow

Create Task (/ccpm:planning:create)
  ↓
Planning Complete → Suggest: Start/Insights/Auto-Assign
  ↓
Start Implementation (/ccpm:implementation:start)
  ↓
Work on Subtasks → Auto-suggest next (/ccpm:implementation:next)
  ↓
All Complete → Suggest: Quality Checks
  ↓
Quality Checks (/ccpm:verification:check)
  ↓
Checks Pass → Suggest: Verification
  ↓
Verification (/ccpm:verification:verify)
  ↓
Passes → Suggest: Finalize
  ↓
Finalize (/ccpm:complete:finalize)
  ↓
Done → Suggest: New Task/Report

[At any point]:
- /ccpm:utils:context - Resume quickly
- /ccpm:utils:status - Check status
- /ccpm:utils:report - Project overview
- /ccpm:utils:insights - Get AI analysis
- /ccpm:spec:sync - Keep spec in sync with reality

🚀 Quick Start

First Time

# Day 1: Create your first task
/ccpm:planning:create "Your task title" your-project JIRA-123

# Follow interactive prompts - it will guide you through everything!

Daily Routine

# Morning: Check project status
/ccpm:utils:report your-project

# Pick a task and load context
/ccpm:utils:context WORK-123

# Let interactive mode guide you from there!

When Stuck

# What should I do next?
/ccpm:implementation:next WORK-123

# What's the full picture?
/ccpm:utils:context WORK-123

# How complex is this really?
/ccpm:utils:insights WORK-123

Project-Specific Commands

/ccpm:my-project:check-pr <pr-number-or-url> 🆕

Comprehensive BitBucket PR analysis for My Project project.

What it does:

• Browser MCP selection (Playwright or Browser MCP)
• Authentication pause for manual sign-in
• Build status analysis with fix suggestions
• SonarQube quality gate review
• Code quality assessment
• Test coverage analysis
• Security vulnerability detection
• Jira ticket integration (read-only)
• Interactive fix workflow
• Export detailed reports

# Check PR by number
/ccpm:my-project:check-pr 123

# Check PR by full URL
/ccpm:my-project:check-pr https://bitbucket.org/my-project-dev/my-project-mobile-app/pull-requests/456

Features:

• ✅ Flexible browser MCP choice
• 🔐 Manual authentication support (pauses for sign-in)
• ⛔ Never mutates BitBucket/SonarQube without explicit approval
• 📊 Comprehensive quality analysis
• 💡 Actionable fix suggestions with code examples
• 📝 Draft PR comments for review before posting
• 📄 Export analysis to markdown
• 🎯 Interactive next-action workflow

Safety:

• All write operations require explicit confirmation
• Shows exact content before posting anything
• Respects SAFETY_RULES.md throughout

📁 Directory Structure

`$CCPM_COMMANDS_DIR/`
├── README.md (this file)
├── SAFETY_RULES.md
├── spec/ (NEW - Spec Management)
│   ├── create.md - Create Epic/Feature with spec doc
│   ├── write.md - AI-assisted spec writing
│   ├── review.md - Spec validation & grading
│   ├── break-down.md - Epic→Features, Feature→Tasks
│   ├── migrate.md - Migrate .claude/ specs to Linear
│   └── sync.md - Sync spec with implementation
├── planning/
│   ├── create.md - Create + plan in one step
│   ├── plan.md - Populate existing issue
│   └── quick-plan.md - Quick planning (no Jira)
├── implementation/
│   ├── start.md - Start with agent coordination
│   ├── next.md - Smart next action detection
│   └── update.md - Update subtask status
├── verification/
│   ├── check.md - Quality checks
│   ├── verify.md - Final verification
│   └── fix.md - Fix verification failures
├── complete/
│   └── finalize.md - Post-completion workflow
├── my-project/ (NEW - My Project Project)
│   └── check-pr.md - Comprehensive PR analysis
└── utils/
    ├── _shared.md (Interactive mode patterns)
    ├── _interactive_mode_template.md
    ├── status.md
    ├── context.md (NEW)
    ├── report.md (NEW)
    ├── insights.md (NEW)
    ├── auto-assign.md (NEW)
    ├── sync-status.md (NEW)
    ├── rollback.md (NEW)
    ├── dependencies.md (NEW)
    ├── help.md (NEW)
    ├── cheatsheet.md (NEW)
    └── agents.md

🎉 Summary

PM Commands 2.0 transforms your workflow from:

• ❌ Manual, disconnected commands
• ❌ Constant context switching
• ❌ Forgetting what's next

To:

• ✅ Continuous, guided workflow
• ✅ Intelligent next-action suggestions
• ✅ One-click command chaining
• ✅ Full automation with safety

Try it now:

/ccpm:planning:create "Your next big feature" your-project

Let interactive mode guide you to completion! 🚀