implementing

To implement a scoped issue, make the code change within the assigned tree and branch, verify it using brief-provided commands, and open a draft pull request with handoff context. This keeps implementation focused on the assigned workstream without drifting into review coordination.

The best way to hand off a verified code change is to run the exact verification commands required by the brief, validate the scoped diff, and open one draft pull request with context. Note what is out of scope and run the PR engine once for initial routing.

No, this implementation workflow does not handle review coordination or merge duties. It applies to role-scoped implementation tasks that require staying inside an assigned tree and branch, focusing solely on making the code change, verifying it, and opening a draft pull request for handoff.

You need to run verification commands before opening a draft PR because verification discipline ensures the scoped implementation is validated against the brief's requirements. This prevents unverified changes from being routed for review, maintaining a clean handoff for the next stage.

Yes, you can use this approach for a bug fix or feature slice. An agent updates the code and tests, verifies the result with the provided commands, and leaves a complete draft pull request with handoff context for the next stage, ensuring disciplined implementation.

You should avoid using a scoped draft PR workflow when a task requires review coordination, merge duties, or decisions outside the brief's assigned tree and branch. This workflow is strictly for making scoped code changes, verifying them, and handing off via a draft pull request.