Implement

Use implement to turn settled work into verified changes. It is an execution router, not a planning replacement.

Boundaries

Start from an approved spec, plan, issue, or a small direct request whose behavior is already decision-complete.
If the source artifact says to pause for approval, stop until approval exists.
If product behavior, API contracts, UI direction, invariants, or error behavior are unresolved, stop and route back to spec, design-doc, or grilling.
If the work is too broad to execute safely in one pass, route to plan for portable task splitting.
If the hard part is sequencing, handoff, recovery, or durable proof across sessions, route to plan.
Do not commit, push, deploy, or close tracker items unless the user asks or the repo workflow explicitly requires it.