approve
Approve the current PRD and begin parallel story execution. Analyzes dependencies, creates…
Resume an interrupted mega-plan execution. Detects current state from existing files and continues automatically. Usage: /plan-cascade:mega-resume [--auto-prd]
> /plugin marketplace add Taoidle/plan-cascade > /plugin install plan-cascade@plan-cascade
How it fires
How this command gets triggered: by you, by Claude, or both.
/mega-resumeContext preview
What this command does when you run it.
Resume an interrupted mega-plan execution. Detects current state from existing files and continues automatically. Usage: /plan-cascade:mega-resume [--auto-prd]
description: "Resume an interrupted mega-plan execution. Detects current state from existing files and continues automatically. Usage: /plan-cascade:mega-resume [--auto-prd]"
Resume execution of an interrupted mega-plan by detecting the current state from existing files.
This command works with both new and legacy path storage modes:
Files are stored in user data directory:
File locations:
All files in project root:
The command auto-detects which mode is active and scans the appropriate directories.
**To avoid command confirmation prompts during automatic execution:**
1. **Use Read tool for file reading** - NEVER use `cat` via Bash
2. **Use Glob tool for finding files** - NEVER use `ls` or `find` via Bash
3. **Use Grep tool for content search** - NEVER use `grep` via Bash
4. **Only use Bash for actual system commands:**
**Compatibility**: Works with both old-style (pre-4.1.1) and new-style mega-plan executions.
# Get mega-plan path from PathResolver
MEGA_PLAN_PATH=$(uv run python -c "from plan_cascade.state.path_resolver import PathResolver; from pathlib import Path; print(PathResolver(Path.cwd()).get_mega_plan_path())" 2>/dev/null || echo "mega-plan.json")
if [ ! -f "$MEGA_PLAN_PATH" ]; then
echo "============================================"
echo "ERROR: No mega-plan.json found"
echo "============================================"
echo "Searched at: $MEGA_PLAN_PATH"
echo "Nothing to resume."
echo "Use /plan-cascade:mega-plan <description> to create a new plan."
exit 1
fiRead all available state information:
cat mega-plan.json
Extract:
cat .mega-status.json 2>/dev/null || echo "{}"Extract:
For each feature in mega-plan.json:
# Get worktree base directory from PathResolver
WORKTREE_BASE=$(uv run python -c "from plan_cascade.state.path_resolver import PathResolver; from pathlib import Path; print(PathResolver(Path.cwd()).get_worktree_dir())" 2>/dev/null || echo ".worktree")
FEATURE_NAME="<feature-name>"
WORKTREE_PATH="$WORKTREE_BASE/$FEATURE_NAME"
# Also check legacy location if worktree not found in new location
if [ ! -d "$WORKTREE_PATH" ] && [ -d ".worktree/$FEATURE_NAME" ]; then
WORKTREE_PATH=".worktree/$FEATURE_NAME"
fi
# Check worktree existence
if [ -d "$WORKTREE_PATH" ]; then
WORKTREE_EXISTS=true
# Check for PRD
if [ -f "$WORKTREE_PATH/prd.json" ]; then
PRD_EXISTS=true
# Count stories
TOTAL_STORIES=$(jq '.stories | length' "$WORKTREE_PATH/prd.json")
fi
# Check progress.txt for markers
if [ -f "$WORKTREE_PATH/progress.txt" ]; then
# New-style markers
PRD_COMPLETE=$(grep -c "\[PRD_COMPLETE\]" "$WORKTREE_PATH/progress.txt" 2>/dev/null || echo "0")
STORIES_COMPLETE=$(grep -c "\[STORY_COMPLETE\]" "$WORKTREE_PATH/progress.txt" 2>/dev/null || echo "0")
FEATURE_COMPLETE=$(grep -c "\[FEATURE_COMPLETE\]" "$WORKTREE_PATH/progress.txt" 2>/dev/null || echo "0")
# Old-style markers (compatibility)
OLD_COMPLETE=$(grep -c "\[COMPLETE\]" "$WORKTREE_PATH/progress.txt" 2>/dev/null || echo "0")
fi
fiFor each feature, determine its state based on available evidence:
Feature State Detection Logic: 1. NO WORKTREE EXISTS: → State: "pending" → Action: Create worktree, generate PRD, execute stories 2. WORKTREE EXISTS, NO prd.json: → State: "worktree_created" → Action: Generate PRD, execute stories 3. WORKTREE EXISTS, prd.json EXISTS but EMPTY (no stories): → State: "prd_incomplete" → Action: Regenerate PRD, execute stories 4. WORKTREE EXISTS, prd.json HAS STORIES, NO completion markers: → State: "prd_generated" → Action: Execute stories (PRD might be from old version) 5. [PRD_COMPLETE] marker exists, NO [FEATURE_COMPLETE]: → State: "executing" → Action: Continue/resume story execution 6. [FEATURE_COMPLETE] marker exists: → State: "complete" → Action: Ready for merge 7. Status in .mega-status.json says "merged": → State: "merged" → Action: Skip (already done) COMPATIBILITY: Old-style detection - If prd.json has stories with status="complete", count them - If all stories complete but no [FEATURE_COMPLETE] marker: → State: "complete" (old-style completion) → Action: Ready for merge
===============================================
AI-Powered Cascading Development Framework Transform complex projects into parallel executable tasks with intelligent decomposition and multi-provider execution Why Plan Cascade? • Product Editions • Quick Start • Architecture
Repo: Taoidle/plan-cascade
Approve the current PRD and begin parallel story execution. Analyzes dependencies, creates…
AI auto strategy executor. Analyzes task and automatically selects and executes the best…
Check and update .gitignore to exclude Plan Cascade temporary files. Ensures planning files…
Complete a worktree task. Verifies all phases are complete, commits code changes (excluding…
Show execution status dashboard. Usage: /plan-cascade:dashboard [--verbose|-v] [--json]
Generate a technical design document. Auto-detects level: project-level from mega-plan.json,…