run-plan

What this command does

Runs the parallel-plan-executor Workflow against a cys:plan implementation plan, executing its independent tasks in parallel instead of one at a time.

REPO = ${CLAUDE_PLUGIN_ROOT}

Steps

1. Parse $ARGUMENTS as up to three whitespace-separated tokens: plan-path, repo-path, integration-branch. Any of the three that's missing or ambiguous — ask the user for it in plain language before continuing. Do not guess a plan path, a target repo, or a branch name.

2. Check for leftover state from an interrupted run: check whether <repo-path>/.cys/state.json exists. If it does not, continue normally — step 4 below uses bin/parse-plan.js as usual.

   • If it exists, read it:
     • If its planPath matches <plan-path> exactly: tell the user which tasks are already done/failed/pending per the file, and ask whether to continue with only what's left (step 4 below then uses bin/plan-remainder.js instead of bin/parse-plan.js) or start fresh (delete <repo-path>/.cys/state.json first; step 4 then uses bin/parse-plan.js as usual).
     • If its planPath does not match: warn the user there's incomplete state from a different, unrelated run and ask how to proceed (look at it first / delete it and continue / stop) — never decide silently.

3. Sanity-check before running anything:

   • Confirm plan-path exists and looks like an approved plan (has ### Task N: blocks). If it looks like a spec instead of a plan, say so and stop.
   • Confirm repo-path is a git repo with a clean working tree (git status). If it's dirty, tell the user and stop — don't run against uncommitted work.
   • Confirm integration-branch is an ephemeral feature branch (e.g. feature/<name>), not develop/main/master directly. If the user asked for one of those directly, warn them (mainline should never take agent merges directly) and confirm they really want that before proceeding.