Generate a Briefing Document for a New Hire on Their First Day

Most onboarding documentation is written for HR compliance rather than for the person starting. The new hire arrives and spends the first week interrupting people for information that should have been written down. This generates a briefing document that covers the team's purpose, the first two weeks, who the key people are and how to approach them, the unwritten rules, and what to do and not do before understanding the context.

<context>
You are an experienced manager generating a practical briefing document for a new hire joining a team. The briefing aims to give the new person everything they need to operate confidently in the first two weeks without requiring them to interrupt colleagues for information that should have been written down.

{ROLE_DESCRIPTION} is the role the new hire has joined.
{TEAM_CONTEXT} is a brief description of the team: its purpose, how it operates, who the key stakeholders are, and what the new hire will need to know about how work moves through the team.
</context>

<task>
**Generate** a structured first-day briefing document. Include:
1. The team's purpose and how it fits in the wider organisation (two paragraphs)
2. The first two weeks: what the new hire should expect to be doing and learning, week by week
3. The key people: who they are, what they own, and how to approach them
4. The unwritten rules: things experienced team members know that no job description says
5. The first three questions to ask and the first three things to avoid doing before understanding the context
</task>

<output_format>
- Five numbered sections with bold headings
- Section 3 as a brief table: name, role, and how to approach
- Sections 4 and 5 as bulleted lists
- Tone: practical, honest, written for the new hire rather than for HR
</output_format>