Write Plan

Overview

Turn an approved design into an implementation plan a forgetful agent can execute without inventing scope.

Core principle: each task is independently testable; steps are 2–5 minutes; TDD is the default micro-cycle.

REQUIRED UPSTREAM: grill (and solid for non-trivial boundaries) should already have produced shared understanding. Do not plan while product decisions are still open.

Announce: "Using write-plan to …"

When to Use

• After grill/spec approval, before coding
• Multi-file or multi-step features
• User asks for an implementation plan / task breakdown

When NOT to use: single-line fix with obvious one-test cycle (go straight to tdd); pure exploration.