Plan Implementation

Produce plans another engineer or agent can execute without guessing, and find the ways a plan fails before anyone executes it. Each task names its files, its prerequisites, the command that proves it worked, and the condition that makes it done; behavior is pinned by tests before it changes; irreversible steps carry a rollback. A review walks the plan against its constraints, audits its claims against the repository, and proves each behavioral flaw with a counterexample. Both modes use the same cards: each states how to write a construct and how to spot it done wrong.

Workflow

Write a plan for an agreed change: