Write detailed implementation plans at file-level specificity. Use when breaking a design into executable steps.
Author implementation plans that can be executed without ambiguity.
Write as if the executor is an enthusiastic junior engineer with no project context.
Every step must be self-contained and unambiguous. If someone has to guess what you meant, the plan failed.
Each step in the plan must include:
Each step should take 2-5 minutes to execute. If a step feels larger, break it down further. If it feels smaller, consider combining with an adjacent step.
Steps must be ordered by dependency. No step should reference code that has not yet been created by a prior step. Draw the dependency graph mentally before writing the sequence.
Read the relevant template before producing output:
Read ${CLAUDE_PLUGIN_ROOT}/templates/PLAN.mdRead ${CLAUDE_PLUGIN_ROOT}/templates/DESIGN.mdEvery plan starts with a prerequisites section listing: