Use when you have a PRD, research, and design for a multi-step task, before touching any code.
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the plan skill to create implementation plans."
If the design covers multiple independent subsystems, suggest splitting this into multiple plans. Each plan should produce working, testable, shippable software on its own.
If the user agrees to multiple plans, propose plan groupings for user refinement. Once approved you may proceed.
.ai-dev directory (typically the same as the design doc)<topic>-plan.md (or <topic>-plan-1.md, <topic>-plan-2.md for multiple)For each plan document, write with frontmatter:
---