Let a coding agent work from your project backlog

Use My Architect to give a coding agent a retrievable task, its applicable requirements, and a place to record progress. You can then inspect the same work record without copying each ticket and result between the board and the chat.

Prepare work the agent can execute

Define the requested outcome and observable acceptance conditions. Find the existing product capability, link the relevant requirements and source documents, and choose a proportionate work item. A task titled “Implement backend” needs enough context to identify its boundary and expected result.

Follow project workflow when the request is not yet ready for implementation. A backlog entry or recommendation alone does not authorize unrelated work.

Use the current ownership workflow

1. Confirm the project and connect the agent.
2. Read the current epic flow, capabilities, and applicable context.
3. Reuse the authorized epic or enqueue it if needed. The coordinator obtains its own epic claim.
4. Select eligible child work with get_next_child_work and acquire it through the claim_child action of apply_epic_flow_command.
5. Implement the claimed scope, verify it, and retain evidence and a concrete next step.

Recommendations are separate from claims. A coordinator also needs a child claim when implementing an ordinary leaf itself. Existing claims remain with their holders until an explicit supported transition changes ownership.

At meaningful checkpoints, the current holder can use update_progress when live capabilities advertise it. This updates descriptive progress without changing ownership or completion.

Return the result

For completed ordinary child work, save the evidence, use release_child, and then call complete_task without overwriting the original scope with a completion summary. Release and completion are separate guarded operations. If another worker claims the child between them, refresh ownership instead of forcing completion.

Explicitly synchronize proven requirements and linked issues. The coordinator integrates the results and follows delivery verification for the managed epic. Completed children and a merged pull request do not confirm delivery.

The older start_task loop remains relevant only to confirmed unmanaged ordinary work through supported tools. It cannot replace claims or delivery commands for managed work.

Give the agent this task

Work on the accepted payment-recovery backlog in My Architect. Find the
current epic and read its requirements and ownership. Select an eligible
leaf and obtain your own child claim. Implement and verify that scope,
save evidence, and report the next step. Preserve blockers and other
workers' claims; do not infer epic delivery from task completion.

For several workers, use the complete multi-agent coordination guide. For an interrupted session, use resume and handoff.

Verified against app/MCP 1.11.0 and workflow plugin 2.6.0 on October 13, 2026. Confirm the connected server’s capabilities before applying a procedure.