Structured Project Execution

Run large work against a single source of truth on disk so progress survives context loss, session boundaries, and agent handoffs. The discipline: plan → one task in flight → verify → record → repeat.

When to use

Multi-phase features, migrations, anything spanning multiple sessions or where another agent/person may pick up. Skip for single-sitting tasks — the bookkeeping costs more than it saves.

The execution file

Maintain PROGRESS.md (or the project's convention) at the repo root:

# <Project> — Progress

## Goal
<one paragraph: what done looks like>