Write Plan

Overview

A workflow for converting a spec into an executable plan: a numbered list of tasks, each with a file path, an exact change, a test command, and an acceptance check. The skill exists because the most common implementation failure is starting from a plan that says "implement the cache" and discovering at code-review time that "implement" hid four sub-decisions nobody made. A plan written through this skill makes those decisions visible up front. Each task is small enough that a different engineer could pick it up cold; the entire plan is small enough that the spec's acceptance criteria are obviously reachable from it. Used after shape-spec, before code or plan-review.

When to Use