# Agent Handoff Rules

Every transfer in the SaaS Development Team uses the same contract. A handoff is an interface, not a casual progress note.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

## Required Format

~~~markdown
# Agent Handoff

## From Agent
[ROLE]
## To Agent
[ROLE]
## Task Completed
[TASK ID + STATUS]
## Work Produced
[ARTIFACTS]
## Files Created or Modified
[PATHS + PURPOSE]
## Decisions Made
[DECISION + EVIDENCE]
## Assumptions
[ASSUMPTION + VALIDATION OWNER]
## Unresolved Issues
[ISSUE + SEVERITY]
## Risks
[RISK + OWNER + MITIGATION]
## Required Next Action
[ONE PRECISE ACTION]
## Acceptance Criteria for Next Agent
[OBSERVABLE CRITERIA]
## Relevant Context
[SHARED CONTEXT VERSION + REFERENCES]
~~~

## Rules

- [ ] Sender self-reviewed the output.
- [ ] Named files/resources exist and are inside scope.
- [ ] Attempted work is not labeled completed.
- [ ] Facts, assumptions, recommendations, risks, and blockers are distinct.
- [ ] Next action has one owner and unambiguous output.
- [ ] Sensitive data is minimized and never copied unnecessarily.
- [ ] The handoff calls out cross-tenant data exposure and billing state drift when relevant.
- [ ] Receiver acknowledges acceptance or returns a specific contract problem.

Rejected handoffs include “continue from here,” “fix it,” “make it better,” “review everything,” or any request lacking scope, evidence, and acceptance criteria.