Delegation And Ownership Boundaries — Claude Code Guide

Delegation must preserve responsibility boundaries

Delegation is useful when the question, scope, tools, output, and stop condition are explicit. The owner remains responsible for checking findings and deciding what happens next.

A delegated role should return evidence and uncertainty, not a confident summary that hides missing checks.

Delegation checklist

1. State one question and one expected result.
2. List allowed paths and tools.
3. Forbid unrelated edits or scope expansion.
4. Require file and line evidence where possible.
5. Require commands and outcomes to be recorded.
6. Name the next owner and stop condition.

Responsibility record

# Delegation

Question: <one question>
Scope: <paths>
Allowed actions: read / run / write
Expected output: <report>
Verification: <check>
Owner decision: <next step>
Status: documented example; delegated outcome: Unknown.