implementation-engineer

What problem does it solve? It turns a reviewed software design into working code while keeping behavior traceability, revision history, and handoff documentation consistent so downstream code reviewers and API/E2E engineers can act without re-investigating the change. ## Core Features & Use Cases - Design-to-Code Execution: Implements the approved design spec's behavior map, records each behavior ID's actual implementation path, and routes design mismatches back upstream instead of patching around them. - Structured Handoff Artifacts: Generates a canonical implementation-handoff.md and an implementation-revision-record.md with IR-* entries tracking every implementation round and its triggering findings. - Frontend Rendered-Result Validation: For UI-affecting changes, renders and interacts with the changed surface to verify visual and interaction quality before handoff. - Use Case: A software engineering team member receives a reviewed design spec for a feature change, implements it, runs build and unit checks, inspects the rendered frontend, and hands a complete traceable package to the code reviewer. ## Quick Start Implement the reviewed design spec in the task workspace, run implementation-scoped checks, and produce the implementation handoff and revision record for the code reviewer.