st-execute-blueprintlisted

Use when the user asks to run, execute, implement, or carry out a Strikethroo plan or its blueprint by plan ID in this repository — triggers include execute blueprint, run the plan, implement plan, build the plan. Do not use to create a plan, to only generate tasks, to run a single task, or for generic development outside Strikethroo.
e0ipso/strikethroo · ★ 50 · AI & Automation · score 78

Install: claude install-skill e0ipso/strikethroo

# st-execute-blueprint ## Inputs The user supplies the numeric plan ID conversationally. ## Operating Procedure ### 1. Locate the strikethroo root Run `scripts/find-strikethroo-root.cjs` from the user's working directory. If it exits non-zero, stop and ask the user to run `npx strikethroo init`. Treat the path it prints as `<root>` for every subsequent step. Delegated execution workers skip this step and do not emit update notices. Run `scripts/check-for-updates.cjs "<root>"` as a separate command using this skill's script path. Keep the user's working directory. Read the one JSON line on stdout. When `notice` is present, retain its exact text for the final user-facing response. Never pause for permission and never run an update. ### 2. Resolve the plan Run `scripts/validate-plan-blueprint.cjs <plan-id> planFile` for the plan file's absolute path. Another field name prints that field instead. If the script exits non-zero, stop and ask the user to confirm the plan ID. Do not guess a different ID. Run `scripts/validate-plan-blueprint.cjs <plan-id> planDir` and treat the printed path as `<plan-dir>`. ### 3. Validate tasks and blueprint existence Run `scripts/validate-plan-blueprint.cjs <plan-id> taskCount` and `scripts/validate-plan-blueprint.cjs <plan-id> blueprintExists`. ### 4. Auto-generate tasks and blueprint if missing If `taskCount` is 0 or `blueprintExists` is `no`: Notify the user: "Tasks or execution blueprint not found. Generating tasks automatically.