create-plan
Turn a non-trivial change into a written, reviewable plan under the repo's gitignored tmp/ folder — a README overview plus, when the work is multi-step, numbered step markdown files that can be applie
SKILL.md.github/skills/create-plan/SKILL.md
GitHubPlan a change
Create tmp/<plan>/, or use the existing folder the user supplied. Planning changes documents only, not implementation or Git state.
Keep it small
README.md: goal, scope, and the ordered steps.01-topic.md,02-topic.md, etc.: outcome, dependencies, implementation outline, and acceptance checks.
Use Status: pending and Depends on: in each step. Keep steps reviewable: one step per PR, unless the user combines related steps. A small single-step plan can stay in its README.
No required plans/ layer, parent indexes, handoff, or extra document set. Add supporting material only when it helps the work.
Make it useful
Inspect the relevant source first. Describe the intended behavior, owning modules, important decisions, and how success and failure will be verified. Include affected callers and removal of replaced paths. Prefer plain language and outcomes over file-by-file recipes.
Follow the project standards. Link required validation rather than copying rules into every step. Preserve useful existing decisions and evidence; update stale notes instead of adding competing instructions.
Apply a numbered file with apply-step, or the whole folder with apply-plan.