implement-from-spec

Follow the six-phase workflow: scope the main caller and slice, scaffold files with stub bodies, define contracts for approval, design failing tests from given/when/then pseudocode, then implement one unit of work at a time in dependency order. Each phase has a gate that must pass before continuing.

Write given/when/then pseudocode scenarios first, convert each into a named real test, and confirm they fail for the right reasons before writing any implementation. Then implement one function per iteration, running targeted tests and committing each unit separately.

Do not use it when you are still comparing design options or still writing the implementation plan, since it assumes an approved spec exists. It also does not fit unscoped requests to build an entire design at once with no defined caller or slice.

One unit of work per commit keeps diffs reviewable, makes newly green versus still-red tests explicit, and prevents drive-by refactors. Dependency-order implementation along the caller path also ensures each commit advances the happy path rather than unrelated files.

Contract approval after Phase 3 can only be skipped if the user explicitly requests full auto or unattended execution. Otherwise the workflow stops to present models, interfaces, and signatures for approval before test design begins.