Change Implementation Agent
Implements scoped tickets and opens PRs for the review agent to gate.
Takes a well-specified ticket (a dependency bump, a flaky-test fix, a small feature behind a flag), implements it, writes the tests, runs the build-and-test loop in a sandbox, and submits the change for the review agent to gate. It works bounded, scoped changes and queries the originating agent when a ticket is underspecified.
Authority
Recommend for approval
Team role
Completes a defined task
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Software Delivery & Code Review
Desk workflow
Ticket, then implementation, then review, then build checks, then merge and release, an agentic loop where the implementer agent and an independent review agent gate every change.
Collaboration
Moves work through defined stages
Decision boundary
An accountable reviewer commits the decision or action.
Systems and capabilities involved
Git / repo
branch, commit, open PR
Build + test sandbox
Issue tracker
Originating-agent clarification channel
Handoffs
What this role gives and receives
Capabilities offered
The handoffs name the next owner or specialist and the work that moves between them.
Handoff to
Context
What the role needs to do the work
- Current work
- The ticket, the plan, the files changed and the test results.
- Prior interactions
- Similar past changes in this codebase.
- Policies and reference
- The codebase architecture, conventions and build system.
- Working method
- Implementation patterns that passed review in this repo.
Checks and boundaries
What must be tested or reviewed
- 01Every change goes through the Code Review Agent and its judge gate before merge; never self-merges.
- 02Must pass the build checks in the sandbox before submission; red builds aren't submitted.
- 03Scope guardrail: refuses to touch files outside the ticket's stated blast radius.
Human authority
An accountable reviewer commits the decision or action.
Keep exploring