Check unfinished work before an agent marks it done
My Architect checks modeled blockers and ownership when work changes state. Managed epics also require review and confirmation under an accepted delivery policy. These checks make incomplete project state visible; reviewers still need to inspect the implementation and evidence.
Separate task completion from delivery
Section titled “Separate task completion from delivery”An ordinary hierarchy task can have status done. A managed epic has a separate flow: queued → in-progress → review → delivered. Finishing children does not deliver the epic, and a legacy status update cannot replace a managed transition.
Before completing work, read the applicable requirements, unresolved open questions, and dependencies. Confirm the current claim and save the evidence for the actual artifact revision. Requirements can be global or inherited; the visible node’s first list is not necessarily the complete set.
Handle blockers as work to resolve
Section titled “Handle blockers as work to resolve”Unresolved open questions and unfinished blocking dependencies can prevent completion. A rejected transition should lead to an explicit remaining action: resolve the question, complete the dependency, or correct an inaccurate relationship using verified sources.
Do not remove a valid blocker merely to pass a check. Record the decision and its rationale when a question is resolved. For managed epics, supported wait commands preserve the reason, responsible party, and next step. Account decisions follow their explicit decision workflow; a descriptive progress update cannot clear them.
For ordinary children, an active claim protects the work from generic completion writes. Preserve results, release the claim, and then complete the child using the guarded sequence described in multi-agent coordination.
Verify the result under the project’s policy
Section titled “Verify the result under the project’s policy”Submit review with the complete checked criteria, applicable requirement IDs, artifact revision, and evidence. Inspect every delivery criterion against that same artifact. The confirmation route depends on the recorded policy and capabilities of the current connection.
Relevant source changes can make the review stale. Refresh the affected context, recheck, and submit a new review rather than changing revision numbers to force a transition.
validate_project can identify modeled inconsistencies. It does not execute acceptance tests, inspect a deployment, or prove that a linked report is accurate. Neither a green board nor a passed structural validation establishes every real-world outcome.
Prompt to copy
Section titled “Prompt to copy”Check this work before closing it. Read all applicable requirements and blockers, verify ownership, and inspect evidence for the exact result. Complete ordinary tasks through the supported workflow and confirm the epic only under its accepted delivery policy. Report any unmet condition with a concrete next step.
Use verify delivery for the full review and confirmation sequence, including stale reviews and uncertain outcomes.
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.