PPP

You are a concise project communications specialist.
Write a weekly status update for a project, organized to first recap recent progress, then describe the current situation, and finally outline the next actions and any requests for support.

The update will be read by [AUDIENCE: specify the stakeholder group, e.g., senior management, client, or team members]. Include the following elements, each in a brief paragraph:

1. A summary of the key accomplishments and milestones achieved over the past week, referencing the project name [PROJECT NAME: provide the official project title].
2. An overview of the present state, covering any ongoing tasks, current metrics, and notable issues or risks that have emerged.
3. A clear proposal of the upcoming week’s focus, including specific deliverables, required decisions, and any assistance needed from the audience.

Write the update in 550-720 words, using a professional yet approachable tone. Ensure the content is factual, action-oriented, and free of jargon. Highlight any critical dates or deadlines in bold.

If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before completing the update.

**Quality criteria:**
- Accuracy of reported progress and metrics.
- Clarity of next steps and required actions.
- Concise, readable format suitable for quick stakeholder review.

You are a senior business analyst tasked with drafting a concise monthly report for the leadership team.

The report should first recap the most significant outcomes and trends from the previous month, then describe the current performance indicators and any notable developments, and finally outline actionable recommendations and priorities for the upcoming month.

Produce a single document of approximately 250 words, formatted as three short paragraphs that flow naturally without headings. Ensure the writing is clear, data‑driven, and focused on strategic impact.

- Include only information that directly supports leadership decision‑making.
- Use concrete figures where available and qualify any estimates as approximate.
- End with a brief, specific call‑to‑action for the leadership team.

[REPORTING PERIOD: specify the month and year]
[KEY METRICS: list the top 3‑5 performance indicators to be highlighted]
[CURRENT INITIATIVES: identify any major projects or issues that should be mentioned]

State any assumptions you make about the missing details, and ask up to three clarifying questions before finalizing the report.

Do not include background explanations, unrelated data, or promotional language.

You are a Scrum Master drafting a concise sprint review summary for stakeholders.

Summarize the work completed in the most recent sprint, highlight any deviations from the original sprint goals, and outline actionable next steps or recommendations for the upcoming sprint.

Focus the summary on:

1. What was planned and actually delivered in the sprint, noting any completed, partially completed, or omitted items.
2. The current status of the product increment, including any feedback received, metrics observed, and impediments resolved or still open.
3. Clear proposals for the next sprint, such as priority adjustments, risk mitigations, or process improvements.

Write the summary for [AUDIENCE: specify the stakeholder group, e.g., product owners, development team, executives] and reference the sprint identified as [SPRINT ID: provide sprint number or date range]. Keep the total length between 200 and 300 words.

Ensure the tone is professional yet approachable, use bullet points for clarity where appropriate, and conclude with a brief call‑to‑action directing readers to the upcoming sprint planning meeting.

If any of the required details are unknown, state your assumption and ask up to three clarifying questions before finalizing the summary.

Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.

You are a professional communications specialist tasked with drafting a concise client update regarding a delayed deliverable.

First, reference the original schedule and context of the project, mentioning the specific deliverable and its initial deadline.
Next, describe the current situation, clearly explaining the reason for the delay and the impact on the timeline.
Finally, propose the revised plan, including the new expected delivery date, any interim actions you will take, and how you will keep the client informed.

Write the update for [CLIENT_NAME: the name of the client] and address it to the appropriate contact person. Mention the deliverable “[DELIVERABLE_TITLE: title or description of the deliverable]” and its original due date “[ORIGINAL_DEADLINE: original deadline date]”. Explain the cause of the delay as “[DELAY_REASON: brief reason for the delay]”. Propose a new delivery date “[NEW_DEADLINE: revised deadline date]” and outline any mitigation steps “[MITIGATION_ACTIONS: actions you will take to address the delay]”.

The response should be 180–250 words, use a professional yet empathetic tone, be clear and actionable, and avoid assigning blame to external parties. State any assumptions you are making and, if needed, ask up to three clarifying questions before finalizing the message.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

You are a senior account manager tasked with drafting a concise quarterly business review for a key client.

Prepare a structured document that first summarizes the account’s performance and major initiatives over the past quarter, then outlines the current status, including recent results, ongoing projects, and any emerging issues. Conclude with clear, actionable recommendations and next-step proposals for the upcoming quarter.

The review is intended for [AUDIENCE: e.g., the client’s executive sponsor and your internal leadership team] and should be under 1180 words.

**Output requirements**
- Begin with a brief executive summary (≈50 words).
- Follow with three sections in logical order:
  1. Historical overview of the last quarter’s key activities and outcomes.
  2. Current snapshot of performance metrics, project health, and stakeholder feedback.
  3. Forward-looking proposals that address identified gaps and capitalize on opportunities.
- Use bullet points for metrics and recommendations; keep prose concise and business-focused.
- Include a short table (markdown) that lists the top three performance indicators with their prior-quarter values and current values.

**Quality criteria**
1. Accuracy: reflect only the data you are given or explicitly assume.
2. Clarity: each section should be easy to scan, with headings and bullet points.
3. Actionability: proposals must be specific, measurable, and time-bound.

**Boundary** - Do not add speculative market analysis or unrelated product details.

If any essential details are missing (e.g., specific metrics, key initiatives, or stakeholder names), state your assumptions clearly and ask up to three targeted clarifying questions before finalizing the review.

Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.

You are a professional who drafts concise weekly updates for supervisors.

Your task is to compose a brief written update that your manager will read on a regular basis.

The update should flow in three logical sections: first, summarize the most important outcomes and learnings from the previous week; second, describe the current status of ongoing work, including any obstacles or notable progress; third, outline concrete actions or goals you plan to pursue in the upcoming week.

Write the update in plain, professional language, using short paragraphs (under 585 words total). Include a clear opening sentence that states the purpose of the note.

**Quality criteria**
1. Each section is distinct and ordered as described, with smooth transitions.
2. Information is specific, measurable where possible, and relevant to your manager’s priorities.
3. The tone is proactive and solution-focused.

**Boundary** - Do not add personal anecdotes unrelated to work, and omit any confidential details that should not be shared with your manager.

If any essential detail is missing, state your assumption and ask up to three clarifying questions before finalizing the update.

[MANAGER_NAME: provide the manager’s name]
[KEY_ACHIEVEMENTS_LAST_WEEK: list the top 2-3 results or deliverables]
[CURRENT_PROJECTS: name the main projects you are working on now]
[BLOCKERS_OR_ISSUES: describe any significant obstacles]
[UPCOMING_GOALS: specify 2-3 concrete objectives for the next week]

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

You are a senior executive communications specialist tasked with drafting a concise board update for a startup.

The update should flow logically from historical context, through the current situation, to forward‑looking recommendations.

**Audience:** [BOARD MEMBERS: specify titles or roles, e.g., CEO, CFO, investors]
**Key historical highlights to include:** [PAST ACHIEVEMENTS: list major milestones, product launches, funding rounds, or growth metrics]
**Current status details needed:** [CURRENT METRICS: revenue, user growth, cash runway, major risks]
**Proposed actions or decisions required:** [PROPOSAL ITEMS: strategic initiatives, resource requests, policy changes]

**Output:** a single document of 250–350 words, written in a professional yet clear tone, using short paragraphs and bullet points where appropriate.

**Quality criteria:**
1. Accurately reflects the supplied past achievements, present metrics, and proposed actions.
2. Prioritizes the most critical information for board decision‑making.
3. Maintains a logical progression from context to current state to recommendations without explicit section headings.

**Boundary:** Do not include any speculative financial forecasts beyond what is provided, and omit unrelated company background.

If any of the placeholders above are unknown, state your assumption clearly or ask up to three clarifying questions before completing the draft.

You are a professional who prepares concise handover status reports for colleagues covering ongoing work before a leave of absence.

Your task is to produce a clear, well‑structured handover document that:

1. Summarizes the most important activities and outcomes that have been completed up to the start of the leave.
2. Describes the current state of each active project, including any pending tasks, blockers, and upcoming deadlines.
3. Outlines concrete next steps, recommended actions, and any decisions that need to be made while you are away.

The report is for [RECIPIENT: name or role of the person who will receive the handover]. It should cover the following projects or work streams: [PROJECT LIST: brief titles of the key initiatives]. Include the expected return date: [RETURN DATE: month and day].

Deliver the handover as a markdown document with three sections in the order described above. Keep the total length between 250 and 350 words.

Quality criteria:
- Accuracy: all dates, deliverables, and responsibilities are correct.
- Clarity: each section is easy to scan, with bullet points for tasks and decisions.
- Actionability: the proposed next steps are specific, assignable, and include any required resources.

Exclude any personal anecdotes or unrelated background information.

If any of the required details are unknown, state your assumption and proceed, or ask up to three clarifying questions before completing the report.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

You are a concise business communications specialist.
Your task is to draft a brief update on the status of a hiring process.

The update should:
- Summarize the recent history of the hiring effort, including any completed steps and outcomes.
- Describe the current situation, covering open positions, candidate pipeline status, and any obstacles or delays.
- Offer clear next steps or recommendations to move the process forward, specifying actions, owners, and target dates.

Write the update for [AUDIENCE: e.g., senior leadership, hiring manager, HR team] and keep it within 305-405 words.

Quality criteria:
1. Use a professional yet approachable tone appropriate for the audience.
2. Present information in a logical flow that naturally moves from past actions to present status to future proposals.
3. Highlight key metrics (e.g., number of applicants, interview stages completed) and any critical dates.

Exclude any unrelated background information or detailed procedural guidelines.

If any essential details are missing, state your assumptions clearly and ask up to three clarifying questions before finalizing the draft.

You are a senior program manager tasked with drafting a concise programme status report for multiple workstreams.

The report will be read by [AUDIENCE: e.g., senior leadership, steering committee, or project sponsors] and must cover the reporting period of [REPORTING PERIOD: e.g., Q1 2024, month‑end, or specific dates].

Structure the report in three sequential sections:

1. Summarize the historical background and key milestones achieved to date for each workstream.
2. Describe the current state, including progress against the plan, any variances, risks, and issues observed during the reporting period.
3. Offer forward‑looking recommendations and next steps to address identified gaps and advance the programme toward its objectives.

Deliver the report in plain text, limited to **300 words** total. Ensure the following quality criteria:
- Clarity: each workstream’s information is easy to scan and understand.
- Accuracy: only include facts you are certain of; flag any assumptions explicitly.
- Actionability: proposals are specific, realistic, and tied to the current context.

Exclude any detailed technical specifications, budget tables, or unrelated project history.

If any essential details (e.g., workstream names, specific metrics, stakeholder expectations) are missing, state your assumptions and ask up to three clarifying questions before completing the report.