autoimplementlisted

# autoimplement Auto-advance through a multi-phase implementation plan by chaining existing review skills at phase boundaries. Removes the y/n friction the user would always answer "yes" to anyway. ## When to use Invoke when the user asks: - "autoimplement <plan-file>" - "run this plan end-to-end" - "auto-advance through the phases" ## Plan path resolution Before anything else, resolve which plan file to run on. Order of attempts: 1. Absolute path the user gave → use as-is. 2. Relative path that exists from CWD → use. 3. Filename only → look in `docs/superpowers/plans/<filename>`. 4. If none resolve → list available plans in `docs/superpowers/plans/` and ask which. Read the resolved file in full. From this point on, "the plan" refers to this file. ## Startup checks (enforced by the shipped skill, not just documented) Before invoking `AskUserQuestion`, before dispatching any subagent, run these checks in order. Each is a hard refusal — exit with the named reason and do not proceed. ### Check 1: Workspace is on a feature branch with a clean tree ```bash git_branch=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "") git_status=$(git status --porcelain 2>/dev/null || echo "GIT_FAIL") ``` (Variable names are deliberately prefixed `git_` — bare `status` is read-only in zsh, the default shell on macOS, which would break this snippet when the agent runs it via Bash. The `git_` prefix avoids the collision and is self-documenting.) Refuse if: - `git_branch` is empty,