/epcc-resume

name: epcc-resume
description: Resume multi-session work - runs startup checklist and identifies next action
version: 1.1.0
argument-hint: "[--status|--feature F001|--validate]"

EPCC Resume Command

You are in the **RESUME** phase of the EPCC workflow. Your mission is to quickly orient and identify the next action for continuing multi-session work.

**Opening Principle**: Every session starts with clear context. No progress is lost when handoffs are done right.

@../docs/EPCC_BEST_PRACTICES.md - Comprehensive guide covering clarification strategies, error handling patterns, sub-agent delegation, and EPCC workflow optimization

Arguments

$ARGUMENTS

Resume Modes

Parse mode from arguments:

• **Default** (no flags): Full startup checklist + recommended action
• `--status`: Quick progress summary only (no action recommendation)
• `--feature F001`: Focus on specific feature, show its detailed status
• `--validate`: Run E2E checks on all "verified" features

Prerequisites Check

Before proceeding, verify progress tracking exists:

# Check for EPCC state files
if [ ! -f "epcc-features.json" ] && [ ! -f "epcc-progress.md" ]; then
    # Check for legacy setup
    if [ -f "PRD.md" ]; then
        # Legacy repo detected - trigger migration flow
        trigger_legacy_migration()
    else
        echo "No EPCC progress tracking found."
        echo "Start a new tracked project with: /prd or /epcc-plan"
        exit 0
    fi
fi

If no state files exist, inform user and suggest starting with `/prd` or `/epcc-plan`.

---

Legacy Repo Detection (Migration to EPCC v3)

If `PRD.md` exists but `epcc-features.json` does NOT exist, this is a legacy EPCC repo that predates the v3 tracking system.

Step 1: Detect Legacy State

# Detection logic
legacy_files = {
    "PRD.md": exists("PRD.md"),
    "TECH_REQ.md": exists("TECH_REQ.md"),
    "EPCC_PLAN.md": exists("EPCC_PLAN.md"),
    "EPCC_EXPLORE.md": exists("EPCC_EXPLORE.md")
}

v3_files = {
    "epcc-features.json": exists("epcc-features.json"),
    "epcc-progress.md": exists("epcc-progress.md")
}

if any(legacy_files.values()) and not any(v3_files.values()):
    trigger_migration_prompt()

Step 2: Migration Prompt

Display detection results and offer migration:

📋 **Legacy EPCC repo detected**

Found:
  ✅ PRD.md (Core Features documented)
  ✅ TECH_REQ.md (Technical requirements)  [or ❌ if missing]
  ✅ EPCC_PLAN.md (Implementation plan)    [or ❌ if missing]
  ❌ epcc-features.json (Feature tracking)
  ❌ epcc-progress.md (Session log)

This repo was created with EPCC v2 and doesn't have v3 tracking.

Migrate to EPCC v3 tracking? [Y/n]
  - Y: Parse existing documents, generate tracking files
  - n: Continue without long-running project support

Use AskUserQuestion tool:

{
  "questions": [{
    "question": "Legacy EPCC repo detected (PRD.md found, no feature tracking). Migrate to EPCC v3?",
    "header": "Migrate?",
    "multiSelect": false,
    "options": [
      {
        "label": "Yes, migrate",
        "description": "Parse PRD.md/TECH_REQ.md, generate epcc-features.json and epcc-progress.md"
      },
      {
        "label": "No, skip",
        "description": "Continue without v3 tracking (limited session continuity)"
      }
    ]
  }]
}

Step 3: Migration Execution

If user confirms migration:

3a. Parse PRD.md for Features

Look for feature sections in PRD.md:

• "Core Features" / "Features" / "Functional Requirements"
• Priority markers: P0, P1, P2 or Must Have, Should Have, Nice to Have

Extract each feature:

{
  "id": "F001",
  "name": "[Feature name]",
  "description": "[Feature description]",
  "priority": "[P0/P1/P2]",
  "status": "pending",
  "passes": false,
  "source": "PRD.md#[section]"
}

3b. Enrich with TECH_REQ.md (If Present)

If TECH_REQ.md exists, parse for:

• Technical subtasks per feature
• Infrastructure requirements
• Non-functional requirements

Add subtasks to features:

{
  "subtasks": [
    {"name": "Database schema", "status": "pending"},
    {"name": "API endpoint", "status": "pending"},
    {"name": "Unit tests", "status": "pending"}
  ]
}

Add infrastructure features (INFRA-*):

{
  "id": "INFRA-001",
  "name": "Database Setup",
  "priority": "P0",
  "status": "pending"
}

3c. Generate epcc-features.json

Create the tracking file with all features as pending:

{
  "project": "[Project name from PRD]",
  "version": "3.0.0",
  "created": "[current timestamp]",
  "lastUpdated": "[current timestamp]",
  "migratedFrom": "EPCC v2",
  "migrationDate": "[current timestamp]",
  "sourceFiles": ["PRD.md", "TECH_REQ.md"],
  "WARNING": "Feature definitions are IMMUTABLE. Only modify passes, status, and subtasks[].status fields.",
  "features": [
    // ... extracted features
  ],
  "metrics": {
    "total": X,
    "verified": 0,
    "inProgress": 0,
    "pending": X,
    "percentComplete": 0
  }
}

3d. Initialize epcc-progress.md

Create progress log with migration entry:

# EPCC Progress Log

**Project**: [Project Name]
**Started**: [Original PRD date if available, else today]
**Migrated to v3**: [Today's date]
**Progress**: 0/X features (0%)

---

## Session: Migration - [timestamp]

### Migration from EPCC v2

Imported features from legacy EPCC setup:
- Source: PRD.md, TECH_REQ.md
- Features imported: X
- Infrastructure tasks: Y

### Feature Summary
| ID | Name | Priority | Status |
|----|------|----------|--------|
| F001 | [Name] | P0 | pending |
| F002 | [Name] | P0 | pending |
...

### Next Session
- Review imported features for accuracy
- Mark any already-completed features
- Begin implementation with `/epcc-code [feature-id]`

3e. Git Commit Migration

Stage and commit migration files:

git add epcc-features.json epcc-progress.md
git commit -m "chore: migrate to EPCC v3 tracking system

- Imported X features from PRD.md
- Added Y infrastructure tasks from TE