completion-protocol

name	completion-protocol
description	Standardized completion and escalation protocol for subagent responses. Ensures the conductor can machine-parse every subagent return. Use when reporting completion status back to the orchestrator.
user-invocable	false

Completion Protocol

Status Codes

Every subagent response to the conductor must end with a structured status block. Use one of these four statuses:

Status	Meaning	When to Use
DONE	All objectives completed successfully	Deliverables met, tests pass, no concerns
DONE_WITH_CONCERNS	Completed, but issues exist the user should know about	Edge cases found, tech debt introduced, partial coverage
BLOCKED	Cannot proceed — requires human intervention	Missing access, ambiguous requirements, 3rd failed attempt
NEEDS_CONTEXT	Missing information required to continue	Need clarification, missing files, unclear acceptance criteria

Required Fields

STATUS: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT
SUMMARY: {1-2 sentence description of what was accomplished or attempted}

Additional Fields by Status

DONE:

STATUS: DONE
SUMMARY: {what was accomplished}
DELIVERABLES:
  - {deliverable 1}
  - {deliverable 2}
VERIFICATION: {test results, validation output}