Write a task or project handover document

**Role:** You are a Team Lead creating a handover document for {handover_context} — either a role transition, project handoff, or task transfer.

**Context:**
Handovers fail when the incoming person doesn't have the context to make good decisions. A great handover document is not a status report — it is an operational manual that helps the new owner understand the 'why' behind current decisions, not just the 'what'. The handover is from {current_owner} to {new_owner}.

**Task:**
Write a comprehensive handover document that would allow {new_owner} to operate independently from Day 1. Think about what you wish someone had told you when you started. Include the non-obvious context.

**Input Available:**
- {handover_context}: What is being handed over (project, role, task, account)
- {current_status}: Current state of all active work
- {current_owner}: Person handing over
- {new_owner}: Person receiving the handover
- {transition_date}: When the handover takes effect
- {key_relationships}: Important contacts and their role
- {known_issues}: Ongoing problems, blockers, or sensitive situations
- {recurring_tasks}: Regularly occurring responsibilities with cadence

**Output Format:**
1. Overview: What this role/project/task is and why it matters
2. Current status snapshot: Active workstreams | Status | Next action | Owner post-transition
3. Recurring responsibilities calendar: Task | Frequency | How to do it | Tools used | Contacts
4. Key relationships: Name | Role | Context | Communication preference | Current relationship status
5. Open issues and landmines: What's unresolved, sensitive, or about to become a problem
6. Decisions made and their rationale (so new owner doesn't relitigate settled issues)
7. Resources and access: Tools, logins, documentation, and where to find what
8. First 30 days recommended actions for the incoming owner

**Guardrails & Quality Control:**
- Include the 'landmines' — things that look fine but have history or sensitivity
- Do not omit recurring tasks even if they seem obvious — what's obvious to you is invisible to the new owner
- Write for someone who has no context — avoid acronyms or shorthand without explanation
- Every open issue must have a clear recommended next action