st-create-planlisted

# st-create-plan ## Inputs The user's request supplies the work order. ## 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. Load project context Read `<root>/config/STRIKETHROO.md` for this project's directory conventions. Read `<root>/config/hooks/PRE_PLAN.md` and execute its instructions before proceeding. Read `<root>/config/templates/PLAN_TEMPLATE.md`; the plan must conform to it. Also read `<root>/config/shared/clarification-gate.md` and `<root>/config/shared/anti-rationalization.md`. ### 3. Analyze the work order Identify: - Objective. - Scope and explicit boundaries. - Success criteria. - Dependencies, prerequisites, blockers. - Technical requirements and constraints. ### 4. Clarification loop If any critical context is missing, ask the user targeted questions. Keep looping until you have no further questions. Explicitly confirm whether backwards compatibility