Bring in the requirement
Attach the story and the acceptance criteria that define the requested behavior.
Developer / Software delivery
Build from the reasoning behind the request.
Developer brings engineering knowledge into the task, so agents and reviewers can work from the specifications and architectural decisions that explain what a change should do.
Delivery contextDeveloper
Add currency validation using the billing specification and the API decision record.
In the workspace
Product specification
INV-214 · Reject unsupported currency codes
Architecture decision
ADR-028 · Validate at the API boundary
Implementation scope
Validation change and tests · Prepared for review
Keep the implementation aligned with its specification.
How it works in Developer
The engineer starts with an explicit requirement and can review the implementation against the decisions that shaped it.
Add engineering knowledge
Include the architectural decisions and documentation relevant to the change.
Review against intent
Use that context to assess whether the implementation solves the right problem.
Bring Developer to your team.
Explore delivery context around your company’s workflows.