Implement

Execute a clear change without re-deciding product or architecture unnecessarily.

Entry

Use when a plan is ready or a bounded task is sufficiently clear to implement directly. If substantial behavioral/architecture ambiguity remains, route back to shape/architect/plan rather than guessing.

Workflow

1. Reality-check the branch, intended base, current code, and working tree. Preserve unrelated changes.
2. For substantial work, verify prerequisites with a lightweight gate.
3. Implement one coherent behavior slice at a time. Prefer existing patterns and dependencies.
4. Keep business/domain intent separate from vendor/framework plumbing where the project architecture already does so.
5. Run the cheapest useful static/build evidence after meaningful slices.
6. Add targeted regression/integration coverage appropriate to the risk. Do not force red-green-refactor unless TDD was explicitly selected.
7. Avoid unrelated cleanup and refactors unless required for correctness or explicitly accepted.