leader-developer-handoff-contractlisted

# Leader → Developer Handoff Contract ## Native mechanism Claude Code's [Subagents](https://code.claude.com/docs/en/subagents) feature already gives a dispatched agent "its own context window with a custom system prompt, specific tool access, and independent permissions" — but the platform doesn't require or shape what goes in the dispatch *prompt* itself. This skill is the discipline layer on top: the 6 elements a prompt must contain regardless of how well-configured the subagent's own definition is. ## When to invoke - About to dispatch a sub-agent (Developer / Designer / Code Reviewer / drafting agent). - Writing the dispatch prompt. - User asks "what should the sub-agent dispatch include / which elements am I missing". ## The 6 required elements Every dispatch prompt must contain: ### 1. Task scope with verifiable target - One sentence stating the goal. - Explicitly name **the output file / section / behaviour**. - Include a mechanically checkable success / failure condition. **Good**: "Draft §5 Logger for `docs/foundations.md`; output format: complete markdown section; scope: adopt `os.Logger` defaults, with subsystem / category conventions and privacy default" **Bad**: "Write something about logger" ### 2. Files / docs the sub-agent should read - List file names + sections. - Don't say "read design.md"; say "read `design.md §How.2`, `foundations.md §3-§4`". - Add grep targets / line ranges when useful to save the sub-agent's exploration tokens. ### 3. Expli