IMPLEMENTATION
Build the agreed outcome
Check the work against it
GenieWorks carries the accepted specification through coding, verification, and acceptance review. Your team receives a PR with an account of what changed and how it was checked.
Follow the implementation01 · BUILD WITH A SHARED TARGET
The agreement stays beside the code
The accepted handoff defines Web retry identity, API reuse, and permission behavior. GenieWorks implements the selected component work in isolated execution and runs the project’s configured checks.
Then acceptance review checks the committed change against the criteria and implementation checklist. In this example, passing checks still leave one agreed behavior missing.
02 · FIND THE GAP AND FOLLOW THROUGH
The API reuses the export
Web still starts another request
The API change is locally correct, but Web creates a fresh request identity after a lost response. Together, they still produce a duplicate. Review ties that gap directly to AC-01.
GenieWorks corrects the Web retry, adds its regression check, and repeats affected verification and acceptance review. A finding that remains unresolved stays in the report.
Original request req-42
Web retry req-43
Original request req-42
Web retry req-42
New export remains a deliberate action with a fresh identity
03 · REPORT THE WORK
The team can see what was delivered
GenieWorks opens PR #84 and reports the implemented behavior, the gap found and corrected, and the checks performed.
Alex asks for one addition. That changes the agreement, so the update is implemented and reviewed against the revised criteria.
APP-42 · Comments & history
Assigned to GenieWorks · Accepted specification ready for implementation
PR #84 opened. Web/API retry behavior implemented. AC review found and fixed the Web identity gap. Configured checks and acceptance review repeated.
Please also link the retry message to the existing export.
PR #84 updated. The message links to the original export. AC-01 updated; checks and acceptance review repeated.
04 · INSPECT THE HANDOFF
A PR with evidence behind “done”
Inspect the agreement, the missed obligation, and the final report. The final handoff names what changed, what was checked, and what still needs human review.
Open full screenshotHuman review and release remain separate. The report covers the agreed scope and configured checks. It is not a claim of exhaustive testing or production validation.
FROM ONE TASK TO THE NEXT
The workflow carries the discipline
The accepted specification stays the target across coding, review, and repair. Project conventions and configured checks travel with the work. Teammates can inspect the decisions and evidence in the shared issue.
WHEN YOU WANT A DEEPER LOOK
What about the scenarios
the agreement didn’t cover?
Code assurance explores broader interactions and challenges the findings. It is a separate option for deeper investigation.