Worker Reporting

Worker Reporting Format

When you finish your task (or need to exit early), return your results in this exact format:

## STATUS: {DONE | PARTIAL | BLOCKED}

## ACCOMPLISHED
- {bullet list of what you completed}
- {include file paths, commands run, verification results}

## REMAINING
- {what's left to do, if anything}
- {omit this section if STATUS is DONE}

## QUESTIONS
- {questions for the supervisor, if any}
- {information you need to continue}
- {omit this section if you have no questions}

## EVIDENCE
- {command output, test results, or other proof}
- {the supervisor may verify your work — provide evidence}

Status Definitions

Capability Request (Special BLOCKED Pattern)

When you need a knowledge skill you weren't given at launch, use BLOCKED with a NEED_CAPABILITY section:

## STATUS: BLOCKED

## ACCOMPLISHED
- Connected to dev-01 via SSH
- Found auth-service pod running on port 9001

## NEED_CAPABILITY
Skill: worker-database
Reason: I need the PostgreSQL connection string to verify auth-service DB migrations

## REMAINING
- Verify DB schema matches expected migration state
- Report results

The supervisor will either:

• GRANT: Resume you with "CAPABILITY GRANTED: Read ~/.claude/skills/{skill}/SKILL.md and continue."
• DENY: Resume you with "CAPABILITY DENIED: {reason}. Stay within scope."

Rules

• ALWAYS include the STATUS line — the supervisor parses this programmatically
• ALWAYS include ACCOMPLISHED even if empty ("Nothing — blocked immediately")
• Be specific: "Fixed route in /app/routes.py line 42" not "Fixed the route"
• Include EVIDENCE: actual command output, HTTP responses, file diffs
• If BLOCKED: explain exactly what you need so the supervisor can provide it on resume
• If NEED_CAPABILITY: name the exact skill and explain why it's needed for THIS task