st-execute-tasklisted

Use when the user asks to run, execute, or implement one specific task ID within a Strikethroo plan in this repository — triggers include execute task, run task, implement task, do task N. Do not use to execute a whole plan or blueprint, to generate tasks, or for generic development outside Strikethroo.
e0ipso/strikethroo · ★ 50 · AI & Automation · score 78

Install: claude install-skill e0ipso/strikethroo

# st-execute-task ## Critical Rules 1. **Maintain status integrity** — update task status throughout the execution lifecycle. 2. **Document execution** — record all outcomes and issues encountered. ## Inputs The user supplies the numeric plan ID and task 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 the task file Look for `<plan-dir>/tasks/<task-id>--*.md`, then for the zero-padded `<plan-dir>/tasks/0<task-id>--*.md`. If neither matches, list the files in `<plan-