writing-implementation-plans

Installation
SKILL.md

Writing Implementation Plans

A useful plan lets an implementer start the right work, in the right order, without guessing consequential decisions. It connects the agreed outcome to bounded tasks, dependencies, and observable checks. Detail should prevent a costly mistake or lost context, not prescribe every coding move.

This skill is self-contained and focuses on writing, reviewing, and maintaining plans, not managing the entire implementation. Loading it does not authorize implementation, delegation, publishing, or destructive actions.

Choose the Smallest Useful Artifact

  • No new plan: a routine, local change with obvious steps, or execution of an existing plan that still matches the project and requirements. Do not plan merely because several files or steps are involved.
  • Short checklist: a small explicit planning request or a clear single-session task that needs a little sequencing. Chat may be sufficient.
  • Durable plan: work with meaningful cross-component dependencies, staged migration or rollout, costly failure, or context that must survive a session or ownership change. A short but risky change can qualify; size alone is not the test.

Reuse an existing plan and follow the project's document conventions. Save long-lived plans where future implementers can find them; if the location or a new document convention is unsettled and matters, ask rather than inventing a directory or filename convention. A template is not a requirement to create a file.

Keep the agreed approach in the plan unless a separate design/spec is already maintained or has a distinct audience or purpose. Do not create a spec merely because a plan exists. For a separate design record, read references/spec-template.md; link to its authoritative decisions rather than duplicating them.

Ground the Plan Before Writing Tasks

Installs
24
First Seen
9 days ago