st-create-planlisted

Create a new Strikethroo plan for this repository. Use when the user asks to draft, plan, or scope a new strikethroo plan — discovers the local .ai/strikethroo root, runs the project's plan hooks, gathers clarifications, allocates the next plan ID, and writes a Markdown plan conforming to PLAN_TEMPLATE.md. Do not use for generic brainstorming or work outside Strikethroo.
e0ipso/strikethroo · ★ 29 · AI & Automation · score 81

Install: claude install-skill e0ipso/strikethroo

# st-create-plan Drive the end-to-end creation of a new Strikethroo plan for the user's repository. 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's request supplies the work order. 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 create a plan outside of a valid root. For every subsequent step, treat the path printed by this script as `<root>`. ### 2. Load project context Read `<root>/config/STRIKETHROO.md` for the directory structure conventions this project uses. Read `<root>/config/hooks/PRE_PLAN.md` and execute the instructions it contains before proceeding. Read `<root>/config/templates/PLAN_TEMPLATE.md` so the plan you emit conforms to its structure. ### 3. Analyze the work order Identify: - Objective and end goal. - Scope and explicit boundaries. - Success criteria. - Depe