The prompt
Score 10 of 10, Excellent
Use it when A new team member, manager or contractor is joining a running project and needs the context, decisions, people and current state in a few pages.
- {{project_name}}
- {{joiner}}
- {{first_week}}
- {{project_material}}
Full prompt and why it works
Prompt
Project: {{project_name}} Who is joining, their role, and what they will own: {{joiner}} Their first-week priorities, if known: {{first_week}} Project documents and recent material (charter, plan, latest status, decision log, risk log, key emails): """ {{project_material}} """ Task: Write a briefing for the person joining, so that they can understand where the project stands and start on their part within a few days, without reading every document or asking five people the same questions. Format, with these headings: 1. The project in one paragraph: what it is for, who it serves, and the deadline. 2. Where we are now: status, the next milestone and its date, and what is going well or badly, from the latest status. 3. Decisions already made: up to 8, one line each with the date, so they do not reopen settled questions. 4. Open questions and live risks: what is undecided or worrying, and who is handling each. 5. People: who is who, what each owns, and whom to ask about what, as a short table. 6. Their part: what they own, what others are waiting on from them, and the first two or three things to do. 7. Where things are: the documents, trackers and channels mentioned in the material. 8. Words to know: project terms and acronyms, up to 10. Requirements: - Under 800 words. - Use only the material above, and state the date of the latest document, since a briefing built from stale material can mislead. - Do not describe colleagues' performance or tensions between people, even if the emails hint at them; describe roles and responsibilities only. - Copy dates, names and figures exactly. A good briefing is one the joiner can act on in their first week without needing to ask what the project is for. Example of one decisions line's form only, with invented content: "March 3: Phase 1 covers the two pilot sites only (steering group)." If the material contradicts itself, for example two different go-live dates, show both with their sources and mark the point for the joiner to confirm with the project lead.
Variables
- {{project_name}}
- The project's name.
- {{joiner}}
- For example "Alex, contract business analyst, owning user testing".
- {{first_week}}
- For example "meet the site leads; review the test plan". Write "not set" if unknown.
- {{project_material}}
- The charter, latest plan and status, decision and risk logs, and key recent emails, with their dates.
Why it works
- Who it's for. Written for one named person and the part they will own, the briefing gets them working within days instead of reading every document.
- What to avoid. It describes roles and responsibilities only, never colleagues' performance or tensions hinted at in emails, so the briefing is safe to share.
- If unsure. Contradictions such as two go-live dates are shown with their sources, and the date of the latest document is given, so stale material does not mislead.