st-execute-blueprintlisted

# st-execute-blueprint Drive the end-to-end execution of an existing Strikethroo plan blueprint. The skill is assistant-agnostic and self-contained: every script it invokes lives under this skill's `scripts/` directory and is referenced by relative path. ## Critical Rules 1. **Never skip validation gates** — a phase is not complete until `POST_PHASE.md` succeeds. 2. **Preserve dependency order** — never execute a task before all of its dependencies are completed. 3. **Maximize parallelism within each phase** — run all tasks whose dependencies are satisfied simultaneously. 4. **Fail safely and document everything** — halt on unrecoverable errors, and record all decisions, issues, and outcomes under "Noteworthy Events" in the execution summary. ## Inputs The user supplies the numeric plan ID conversationally. Treat it as the only authoritative source of intent. Do not invent answers to clarifying questions — prompt the user instead. ## Operating Procedure ### 1. Locate the strikethroo root Run `scripts/find-strikethroo-root.cjs` from the user's working directory. The script walks up looking for `.ai/strikethroo/.init-metadata.json` and prints the absolute path of the resolved root on success. If the script exits non-zero, the working directory is not inside an initialized strikethroo workspace. Stop and ask the user to run the project initializer (e.g. `npx strikethroo init`) before continuing. Do not attempt to execute a plan outside of a valid root. For every subseq