Emails, reports, meetings, and professional communication done right

Write a professional email for the following situation. Situation: [DESCRIBE WHAT YOU NEED TO COMMUNICATE] Recipient: [role/relationship — manager / colleague / client / vendor / unknown] Context: [any relevant background they need to understand] My goal: [what outcome do I want from this email?] Tone: [formal / semi-formal / direct / diplomatic] The email should: - Subject line: clear, specific, action-oriented - Opening: appropriate, not "I hope this email finds you well" - Body: organised with clear paragraphs or bullets if listing items - Closing: appropriate CTA or next steps - Sign-off: matching the formality level Additional notes: [any constraints — character limit, must mention X, avoid Y] Also write: an alternative version that is [more formal / more direct / shorter] if I need it.

Turn these meeting notes into a professional meeting summary. Meeting notes (raw): [PASTE YOUR NOTES] Meeting type: [standup / project review / client call / strategy session / 1:1] Attendees: [list or number] Meeting date: [DATE] My role: [note-taker / facilitator / participant] Output format: 1. **Meeting summary** (2-3 sentences — the TL;DR) 2. **Key decisions made** (bullet list, numbered) 3. **Action items** table: | Action | Owner | Due Date | Priority | 4. **Open questions** (unresolved items for next meeting) 5. **Next meeting** (date, agenda items) Style: concise, professional, no padding — this goes straight into Slack/email

Write a project proposal for [PROJECT NAME / IDEA]. Context: - Who is approving this: [stakeholder role] - Budget requested: [AMOUNT or "TBD"] - Timeline: [DURATION] - Team needed: [SIZE / ROLES] - Problem this solves: [THE BUSINESS PROBLEM] Proposal structure: 1. Executive Summary (half page — what, why, outcome) 2. Problem Statement (current situation + cost of inaction) 3. Proposed Solution (what you're building/doing) 4. Timeline (phases with milestones) 5. Budget breakdown (detailed) 6. Expected ROI / Success metrics 7. Risks and mitigations 8. Why now (urgency) 9. Next steps (what you need them to do) Tone: [confident / data-driven / persuasive / straightforward]

Help me prepare for this difficult workplace conversation. Situation: [DESCRIBE WHAT HAPPENED AND WHAT NEEDS TO BE ADDRESSED] My role: [manager / peer / employee] Other person's likely reaction: [defensive / upset / dismissive / cooperative] My desired outcome: [WHAT DO I WANT FROM THIS CONVERSATION] Relationship importance: [must maintain / damaged / new / long-term] Provide: 1. Opening line (how to start without immediately triggering defensiveness) 2. How to state the issue clearly (facts, not feelings/judgements) 3. How to listen and respond to pushback 4. 3 likely responses from them + how to handle each 5. How to close with a clear next step 6. What to do if it doesn't go well Also: what NOT to say (phrases that escalate this type of conversation)

Write a [self-review / peer review / manager review] for [ROLE/PERSON] covering [PERIOD]. Information about the work: - Key projects completed: [LIST WITH BRIEF OUTCOMES] - Goals set at start of period: [LIST] - Goals achieved: [LIST WITH METRICS IF POSSIBLE] - Challenges encountered: [DESCRIBE] - Areas of growth: [DESCRIBE] - Development needed: [BE HONEST] Review type: [self-evaluation / 360 feedback / annual review / probation review] Platform format: [free text / ratings with comments / structured form] Write: - Overall performance summary (3-4 sentences) - Achievement highlights (specific, quantified where possible) - Areas for growth (constructive, not critical) - Goals for next period (SMART goals) - Final rating justification (if ratings are used)

Write a [REPORT TYPE: monthly / quarterly / incident / analysis] report for [AUDIENCE]. Report purpose: [WHAT DECISION OR UPDATE DOES THIS SUPPORT] Data/information I have: [PASTE OR DESCRIBE YOUR DATA] Key metrics to include: [LIST METRICS] Period covered: [DATE RANGE] Report structure: 1. Executive Summary (key findings + recommendation — for busy readers) 2. Background/Context 3. Findings (organised by theme, not by data dump) 4. Analysis (what the data means) 5. Recommendations (numbered, specific, actionable) 6. Appendix (raw data / methodology) Visual suggestions: [what charts or tables to include] Tone: [formal / data-driven / strategic / operational] Length: [1 page / 2-4 pages / comprehensive]

Write the [SECTION NAME] section of a business plan for [BUSINESS NAME / TYPE]. Section to write: [Executive Summary / Market Analysis / Product/Service Description / Marketing Strategy / Financial Projections / Operations Plan / Competition Analysis] Business details: - What the business does: [DESCRIPTION] - Target market: [WHO AND HOW BIG] - Revenue model: [HOW IT MAKES MONEY] - Stage: [idea / MVP / early revenue / growth] - Location/market: [WHERE] For this section, include: [Specific requirements based on the section — I'll adapt based on what's requested] Format for: [investor pitch / bank loan / internal planning / accelerator application]

Create an OKR (Objectives and Key Results) framework for [TEAM / INDIVIDUAL / COMPANY]. Context: - Organisation type: [startup / enterprise / team / personal] - Time period: [quarterly / annual] - Top priorities: [WHAT MATTERS MOST RIGHT NOW] - Current challenges: [WHAT'S BLOCKING PROGRESS] - Previous wins: [WHAT WORKED LAST PERIOD] Create [3-5] Objectives, each with 3 Key Results. Rules I want you to follow: - Objectives: inspiring, qualitative, directional - Key Results: measurable, binary clear, 0-100% achievable with stretch - No activities as KRs ("launch X" → "X reaches Y users by date") - Add a confidence score (0-100%) for each KR - Flag any OKRs that conflict with each other Also: explain the grading system and what counts as success.