plan-execution

Plan Execution

Break an approved plan into tasks sized for a single agent context window, then execute them as subagents. Sequential tasks run directly on the main checkout; parallel tasks use git worktrees for isolation and are squash-merged back afterward.

If the plan fits a single context window, still use this skill: it produces one task and executes directly.

Prerequisites

Verification tools

Check that CLAUDE.md documents the project's verification tools (build, lint, static analysis, test commands). Execute agents rely on these to validate their work. If they're missing, tell the user: establishing verification standards comes before running a plan.

Worktree init

Worktree init is only needed when the plan has parallel tasks (which use git worktrees). If the plan is purely sequential, skip this section.

Worktrees must branch from the current HEAD so that parallel tasks see work committed by prior sequential tasks. Check .claude/settings.json for "worktree": { "baseRef": "head" }. If missing, add it (via Bash/python, since direct Edit on that file is blocked). The default (fresh) branches from origin/<default-branch>, which misses all feature-branch commits.

Check whether CLAUDE.md has a ## Worktree init section. If it does, resolve the gather/apply variables before running the workflow:

1. Parse the Gather block, where each line has the form NAME — command. Run each command via Bash in the main checkout and capture its stdout (trimmed).
2. Parse the Apply block, where each line is a shell command that may reference ${NAME} variables from the gather step. Substitute the gathered values into each command. Make symlink commands idempotent: replace ln -s with ln -snf so re-runs don't create circular symlinks inside the existing target.
3. Pass the resolved commands as the worktreeInit arg (string array) to the workflow.

If the section is missing and the plan has parallel tasks, tell the user. Worktree agents without init commands will lack gitignored state, which causes build failures, missing configs, and mid-task recovery friction. Offer to help draft the section before proceeding, the same way you would for missing verification tools.