st-generate-taskslisted

Use when the user asks to decompose, break down, or generate tasks for an existing Strikethroo plan ID in this repository — triggers include generate tasks, break down the plan, decompose plan, create the task blueprint. Do not use to create a new plan, to execute tasks, or for generic project planning outside Strikethroo.
e0ipso/strikethroo · ★ 50 · AI & Automation · score 78

Install: claude install-skill e0ipso/strikethroo

# st-generate-tasks ## 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. ### 3. Load project context Read these files, in order: - `<root>/config/STRIKETHROO.md` — project and directory conventions. - The plan body at the path returned by step 2 — the contract for what tasks must exist. - `<root>/config/templates/TASK_TEMPLATE.md` — the schema every task file must match. - `<root>/config/shared/anti-rationalization.md` — apply in step 4. ### 4. Analyze and decompose the plan Read the entire plan. Identify all concrete deliverables **explic