delegation-quality

You verify sub-agent delegation outputs by enforcing structured output contracts that require Summary, Files, Verification, and Risks for implementations, and Summary, Evidence, Sources, Risks, and a next step for research. Weak or missing evidence is flagged as non-verified.

Evidence-based delegation is a workflow approach that requires sub-agent results to include verification artifacts rather than unsupported claims. It enforces clear deliverables and flags missing sections or weak evidence as non-verified to trigger follow-up or manual completion.

You enforce output contracts by applying different required sections based on delegation type: implementations must include Summary, Files, Verification, and Risks, while research delegations require Summary, Evidence, Sources, Risks, and a recommended next step.

Yes, delegation quality rules apply to implementation, debugging, review, and research workflows. Any delegated work that must be integrated into a dependable final result is subject to the same evidence-based verification and acceptance criteria.

When a sub-agent returns weak or missing evidence, the delegation quality process flags the output as non-verified. This triggers follow-up actions or manual completion to ensure every final claim is supported by required evidence before integration.

No dependencies or components are required. You ask the agent to use the delegation-quality rules to review or dispatch sub-agents, and the rules enforce evidence-based verification and structured output contracts directly within the workflow.