st-generate-taskslisted

# st-generate-tasks Drive the end-to-end decomposition of an existing Strikethroo plan into atomic Markdown task files. 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. ## 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 generate tasks outside of a valid root. For every subsequent step, treat the path printed by this script as `<root>`. ### 2. Resolve the plan Run `scripts/validate-plan-blueprint.cjs <plan-id> planFile` to obtain the absolute path of the plan file. The same script also accepts these field names (single-field output mode) and exposes them on demand: - `planDir` — absolute path of the plan directory - `taskCount` — number of existing task files in that plan's `tasks/` - `blueprintExists` — `yes` or `no` - `taskManagerRoot` — a