leader-developer-handoff-contractlisted

# Leader → Developer Handoff Contract ## 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 5 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. Explicit skill list to invoke - List the skill names the sub-agent should invoke (with plugin prefix). - Don't assume the sub-agent will guess. - Example: "invoke `swift6-concurrency`, `swiftpm-modularization`, `swift-testing-baseline`; review-style dispatches also list `subagent-review-cycles`". ### 4. Expected return format Pick one explicitly (or custom): - **Code diff** (patch / full-file rewrite) - **Markdown section** (drop into a specified file's §) - **Decision