Workflow State Tracking

This skill provides real-time visibility into your CCPM workflow progress, prevents invalid state transitions, and guides you toward task completion through intelligent next action suggestions.

State Machine Overview

CCPM uses a structured 8-state workflow that progresses from concept to completion. Understanding these states helps you know exactly where you are and what to do next.

The 8 Workflow States

IDEA (💡)
  ↓
PLANNED (📋)
  ↓
IMPLEMENTING (🚀) ←→ BLOCKED (🚫)
  ↓
VERIFYING (🔍)
  ↓
VERIFIED (✅)
  ↓
COMPLETE (🎉)

CANCELLED (❌) - Terminal, can branch from any state

State Definitions

State Properties

• Terminal States: COMPLETE and CANCELLED (no transitions out)
• Blocking States: BLOCKED (prevents progression to VERIFYING)
• Gating States: VERIFIED (required before COMPLETE)
• Reversible States: IMPLEMENTING can return to PLANNED if re-planning needed

State Detection

When you ask "Where am I?", this skill detects your current state by checking:

1. Linear Custom Fields

Most accurate: Reads CCPM custom fields directly from Linear issue

- ccpmPhase: Current state (IDEA, PLANNED, etc.)
- ccpmLastCommand: Last CCPM command executed
- ccpmLastUpdate: Timestamp of last update
- ccpmAutoTransitions: Whether state auto-updates

2. Linear Status Inference (Fallback)

If custom fields missing, infers from Linear status:

• "Backlog" → IDEA
• "Planned", "Todo", "Ready" → PLANNED
• "In Progress", "In Development" → IMPLEMENTING
• "Blocked" → BLOCKED
• "In Review", "Testing" → VERIFYING
• "Verified", "Approved" → VERIFIED
• "Done", "Completed" → COMPLETE
• "Cancelled", "Archived" → CANCELLED

3. Checklist Completion Analysis

Analyzes implementation checklist progress:

• 0-25% complete → Early IMPLEMENTING
• 50-75% complete → Mid IMPLEMENTING
• 80-99% complete → Near VERIFYING
• 100% complete → Ready to VERIFY

4. Git State Detection

Checks for uncommitted changes:

• Changes detected → Still IMPLEMENTING
• No changes → Ready for VERIFYING

Valid Transitions

Each state has specific allowed transitions. Attempting an invalid transition will be prevented with helpful suggestions.

Transition Matrix

IDEA        → PLANNED, CANCELLED
PLANNED     → IMPLEMENTING, IDEA, CANCELLED
IMPLEMENTING → VERIFYING, PLANNED, BLOCKED
BLOCKED     → IMPLEMENTING, CANCELLED
VERIFYING   → VERIFIED, IMPLEMENTING
VERIFIED    → COMPLETE, IMPLEMENTING
COMPLETE    → (terminal - no transitions)
CANCELLED   → (terminal - no transitions)

Confidence Levels

Each transition has a confidence score (0-100) indicating how certain the system is:

• 95%: High confidence (plan ready to implement)
• 85%: Good confidence (checks passing)
• 70%: Medium confidence (re-planning during implementation)
• 50%: Low confidence (requires explicit user confirmation)

Invalid Transition Prevention

The skill prevents invalid workflows and provides helpful corrections:

Common Invalid Transitions

❌ IDEA → IMPLEMENTING (skip planning)
   Suggestion: Run /ccpm:plan first

❌ IDEA → VERIFYING (skip planning + implementation)
   Suggestion: Follow workflow: IDEA → PLANNED → IMPLEMENTING → VERIFYING

❌ PLANNED → VERIFYING (skip implementation)
   Suggestion: Run /ccpm:work to start implementation

❌ IMPLEMENTING → COMPLETE (skip verification)
   Suggestion: Run /ccpm:verify first

❌ VERIFYING → COMPLETE (skip verified state)
   Suggestion: Fix issues and re-verify, then transition to VERIFIED

❌ COMPLETE → IMPLEMENTING (reopen completed task)
   Suggestion: Create new issue for follow-up work

Pre-Condition Checks

Before allowing transitions, the skill validates pre-conditions:

Transition to PLANNED requires:

• ✓ Implementation checklist exists in issue description
• ✓ Basic requirements documented

Transition to IMPLEMENTING requires:

• ✓ Plan exists (checklist section)
• ✓ Linear status allows (not in terminal state)

Transition to VERIFYING requires:

• ✓ Checklist 100% complete (or bypassed)
• ✓ No uncommitted git changes
• ✓ Code review initiated

**Transition to VERIFIED requi

...