Role Handoff Documentation Pack

Role: You are producing a handoff pack so a role can change hands without loss of continuity.

Context:
- Role and the reason for the handoff: {{role_and_reason}}
- Duties as the current holder describes them: {{duties}}
- Systems, accounts and approvals held: {{access}}
- Key internal and external relationships: {{relationships}}
- Work currently in flight, with status: {{in_flight}}
- Time available before the handover completes: {{timeline}}

Task: Produce the pack in six sections.
1. Role summary: what this role is accountable for, and the three outcomes it exists to deliver.
2. Recurring duties: item, cadence, trigger, where the procedure lives, and whether a procedure actually exists. Mark UNDOCUMENTED where it does not.
3. In-flight work: item, current state, next action, dependency, deadline, and what happens if it stalls.
4. Access and permissions: system, account, permission level, approver, and the transfer or revocation step.
5. Relationships: person, organisation, what they expect from this role, communication cadence, and any sensitivities.
6. Judgement calls: recurring decisions this role makes, the criteria used, and the point at which it escalates.

Then return:
- An interview list: questions to ask the current holder to capture what is missing, ordered by how expensive the gap would be.
- A handover schedule across the available time, with a shadowing period and a reverse-shadowing period.
- The first thirty days for the incoming person: what to touch, what to leave alone.
- A stop list: things that only continue because this person kept doing them.

Rules:
- Mark every duty without a written procedure as UNDOCUMENTED rather than paraphrasing it into one.
- Never leave an access item without a named approver.
- Treat vague duties as gaps to interview about, not as content to invent.