Use after a spec exists and before any implementation code is written. Activate for keywords like "plan", "break down", "decompose", "implementation plan", "task list", "what's the order". Produces a numbered task list where each task names the file, the change, the test, and what evidence proves it's done. Always cite file paths and exact commands -- never write a plan with placeholder verbs like "implement" or "set up".
$npx -y skills add duthaho/claudekit --skill write-planInstalls into the current project.
Run `npx skills use "https://github.com/duthaho/claudekit" --skill "duthaho/claudekit/write-plan"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/duthaho/claudekit" that are relevant to the current task. Run `npx skills add "https://github.com/duthaho/claudekit"` and select the relevant skills, then follow their instructions.