# AI Productivity Prompt Pack

Version 1.0  
By ReadyOps AI

Thirty-five battle-tested prompts for busy professionals who need better output from ChatGPT, Claude, and similar models without wasting time on blank-page drafting.

## Who This Is For

This pack is built for operators, founders, managers, chiefs of staff, recruiters, project leads, and individual contributors who need to:

- write clearly under time pressure
- turn messy notes into decisions
- plan projects without missing dependencies
- run tighter weekly reviews
- hire with more consistency
- delegate with less ambiguity
- document repeatable work as SOPs

## How To Use This Pack

Every prompt is written to be copied into ChatGPT or Claude as-is. Replace the bracketed placeholders with your details.

For the best result:

1. Give the model real context, not generic summaries.
2. Paste rough notes, drafts, or bullet points instead of trying to clean them first.
3. Tell the model what "good" looks like: tone, audience, length, deadline, and constraints.
4. Ask for two versions when stakes are high: one conservative, one sharper.
5. Edit the final output for judgment, accuracy, and company-specific details before sending.

## Reusable Prompt Upgrades

Add any of these lines to the end of a prompt when useful:

- "Ask up to 5 clarifying questions before drafting if critical information is missing."
- "Give me a fast first draft, then a stronger final version."
- "Flag weak assumptions, contradictions, and missing information."
- "Show your output in a table first, then provide the polished final text."
- "Keep the language direct, plain-English, and free of corporate filler."
- "Make this sound like a calm, credible operator, not a hype marketer."

## Recommended Input Template

Use this mini-brief when you want stronger results from any prompt in the pack:

```text
Context:
- My role:
- Company/team:
- Goal:
- Audience:
- What has already happened:
- Constraints:
- Deadline:

Source material:
[paste notes, email thread, transcript, draft, or bullets]
```

## Example Output Standard

When you want a polished deliverable, add:

```text
Output format:
1. Final deliverable
2. Key assumptions you made
3. Risks or caveats
4. Optional stronger version
```

---

## 1) Email Drafting

### Prompt 1: Reply With Clarity and Momentum

**Use when:** You need to answer a long email thread quickly without sounding rushed.

```text
Act as a senior operations partner.

I need a response to the email below that is clear, concise, and moves the conversation forward.

Context:
- Relationship to sender: [client / coworker / executive / candidate / vendor]
- My goal: [inform / align / decline / ask for input / reset expectations]
- Tone: [warm / direct / diplomatic / firm]
- Maximum length: [e.g. 150 words]

Email thread:
[paste thread]

Instructions:
- Summarize the key issue in one sentence internally before drafting.
- Write the reply in my voice.
- Make the next step explicit.
- Remove filler, repetition, and apology language unless it is necessary.
- If the thread is unclear, identify what needs clarification.

Output:
1. Subject line if useful
2. Final email
3. Optional shorter version
```

### Prompt 2: Difficult Stakeholder Update

**Use when:** A deliverable is slipping and you need to reset expectations without sounding evasive.

```text
Act as a sharp chief of staff helping me write a stakeholder update.

I need to communicate a delay or risk clearly while preserving trust.

Context:
- Project:
- Original expectation:
- What changed:
- Current risk level:
- New proposed timeline:
- What I need from the recipient:

Notes:
[paste notes]

Instructions:
- Lead with the truth, not the excuse.
- Explain what changed in plain language.
- Show what is being done now.
- Offer a concrete recovery plan.
- Keep it calm and accountable.

Output:
1. Executive version under 120 words
2. Full version under 220 words
3. Suggested subject lines
```

**Example output snippet**

```text
Subject: Timeline update on vendor onboarding

We are going to miss the original Friday handoff by three business days. The blocker is not staffing; it is incomplete data mapping from two source systems. We have already reassigned one analyst, locked the field mapping by Thursday, and will send you a validated test file on Monday.
```

### Prompt 3: Post-Meeting Follow-Up Email

**Use when:** You want a follow-up that captures decisions, owners, and next actions.

```text
Turn the notes below into a strong post-meeting follow-up email.

Audience:
- Attendees:
- Main decision-maker:
- Tone:

Meeting notes:
[paste notes]

Instructions:
- Start with the meeting purpose.
- List decisions already made.
- Separate open questions from committed actions.
- Assign owners and dates where possible.
- Keep it skimmable and useful.

Output:
1. Final follow-up email
2. Action items only list
```

### Prompt 4: Internal Alignment Email

**Use when:** You need buy-in across teams before work starts.

```text
Help me write an internal alignment email for a cross-functional initiative.

Context:
- Initiative:
- Why this matters now:
- Teams involved:
- Decision or support needed:
- Known objections:

Instructions:
- Open with the business reason.
- Make the ask extremely clear.
- Anticipate likely concerns.
- Keep the tone credible and collaborative.
- End with one concrete next step.

Output:
1. Final email
2. Version optimized for executives
3. Three possible subject lines
```

### Prompt 5: Client Recovery Email

**Use when:** Something went wrong and you need to rebuild confidence fast.

```text
Act as a client success lead helping me write a recovery email.

Situation:
- What happened:
- Impact on the client:
- Root cause:
- Immediate fix:
- Long-term prevention step:
- Desired tone:

Instructions:
- Take responsibility without overexplaining.
- Be specific about the fix.
- Avoid defensive language.
- Reassure the client with evidence, not vague promises.

Output:
1. Final email
2. A shorter version for fast send
3. A one-line internal summary of the incident
```

---

## 2) Meeting Summaries

### Prompt 6: Executive Meeting Brief

**Use when:** You need a crisp pre-read before a meeting.

```text
Create a one-page executive meeting brief from the information below.

Meeting:
- Title:
- Participants:
- Goal:
- Desired outcome:
- Time available:

Inputs:
[paste notes, doc excerpts, agenda fragments, or prior emails]

Instructions:
- Summarize the situation in 3-5 bullets.
- Identify the decision needed.
- Highlight risks, tradeoffs, and unresolved questions.
- Propose a recommended path.
- Keep it concise enough to read in under 2 minutes.

Output:
1. Executive brief
2. 3 suggested meeting objectives
3. 5 high-value questions to ask live
```

### Prompt 7: Raw Notes to Clean Summary

**Use when:** You have messy meeting notes and need a useful summary.

```text
Turn the raw notes below into a clean meeting summary.

Raw notes:
[paste rough notes]

Instructions:
- Infer structure from the notes without inventing decisions.
- Separate facts, decisions, actions, and open questions.
- Call out anything ambiguous.
- Use plain-English headings.

Output:
1. Summary
2. Decisions made
3. Action items with owner/date if available
4. Open questions
```

### Prompt 8: Decision Log Builder

**Use when:** A recurring project needs a reliable decision trail.

```text
Create a decision log entry set from the notes below.

Context:
- Project:
- Team:
- Date:

Notes:
[paste notes]

Instructions:
- Extract each decision separately.
- For every decision include: decision, reason, owner, downstream impact, and follow-up.
- If the reason is missing, say "reason not stated" instead of inventing it.

Output format:
Use a markdown table with columns:
Decision | Why it was made | Owner | Impact | Follow-up
```

### Prompt 9: Async Update From Meeting

**Use when:** Stakeholders could not attend and need the signal, not the noise.

```text
Write an asynchronous update for people who missed the meeting.

Audience:
- Who missed it:
- What they care about most:

Meeting notes:
[paste notes]

Instructions:
- Keep it under 200 words.
- Lead with what changed.
- Include only decisions, blockers, and next steps.
- End with whether action is required from the reader.

Output:
Final async update
```

### Prompt 10: Meeting Improvement Debrief

**Use when:** A recurring meeting is wasting time and needs a reset.

```text
Review this meeting information and propose how to improve the meeting design.

Meeting details:
- Meeting name:
- Frequency:
- Typical attendees:
- Current purpose:
- Current agenda:
- Pain points:

Examples or notes:
[paste notes]

Instructions:
- Identify where time is being wasted.
- Recommend what should be async instead.
- Suggest a tighter agenda format.
- Recommend who actually needs to attend.

Output:
1. Diagnostic summary
2. Redesigned meeting structure
3. Sample agenda template
```

**Example output snippet**

```text
Recommendation: Convert status round-robin updates to an async note due 2 hours before the meeting. Reserve live time for blocked decisions, tradeoffs, and cross-team dependencies only.
```

---

## 3) Project Planning

### Prompt 11: Project Kickoff Plan

**Use when:** A new initiative needs structure fast.

```text
Act as an experienced program manager.

Build a practical kickoff plan for the project below.

Project:
- Name:
- Goal:
- Deadline:
- Stakeholders:
- Constraints:
- Known dependencies:

Background:
[paste notes]

Instructions:
- Define scope in plain language.
- Break the work into logical phases.
- Identify the critical path.
- Flag major risks and assumptions.
- Keep the plan realistic for a busy team.

Output:
1. Project overview
2. Phase-by-phase plan
3. Risks and assumptions
4. First 7 days action list
```

### Prompt 12: Workback Schedule Generator

**Use when:** You have a hard deadline and need backwards planning.

```text
Create a workback schedule from the final deadline.

Deadline:
- Final deliverable:
- Date:

Inputs:
- Required milestones:
- Review/approval points:
- Team members:
- External dependencies:

Instructions:
- Work backward from the deadline.
- Add reasonable buffer where risk exists.
- Highlight decision deadlines, not just task deadlines.
- Note what slips if a milestone is missed.

Output:
1. Workback schedule table
2. Critical dependencies
3. Where to add management attention
```

### Prompt 13: Risk Register Starter

**Use when:** You want to surface project risk before it becomes a fire drill.

```text
Build a risk register for this initiative.

Project context:
[paste context]

Instructions:
- Identify operational, stakeholder, technical, timing, and dependency risks.
- Rate each risk as low/medium/high for likelihood and impact.
- Give each risk an early warning signal.
- Suggest a mitigation owner.

Output format:
Markdown table with columns:
Risk | Likelihood | Impact | Early warning signal | Mitigation | Owner
```

### Prompt 14: Blocker Resolution Plan

**Use when:** A project is stuck and you need a practical plan to get unstuck.

```text
Help me create a blocker-resolution plan.

Project:
- Current blocker:
- Why it matters:
- Teams involved:
- Deadline pressure:

Notes:
[paste notes]

Instructions:
- Identify root cause candidates.
- Separate what is known from what is assumed.
- Propose 2-3 realistic resolution paths.
- Recommend the fastest viable option.

Output:
1. Root cause analysis
2. Resolution options
3. Recommended next 3 moves
4. Draft message to stakeholders
```

### Prompt 15: Project Status Memo

**Use when:** Leaders need a fast status read without sitting in a meeting.

```text
Write a project status memo from the notes below.

Notes:
[paste notes]

Include:
- Overall status: green / yellow / red
- What moved forward this period
- What is blocked
- What decisions are needed
- What happens next

Instructions:
- Make the signal obvious in the first 3 lines.
- Avoid generic "on track" language without evidence.
- Highlight concrete dates and owners.

Output:
1. Executive memo
2. 5-bullet version
```

**Example output snippet**

```text
Status: Yellow

The launch date is still achievable, but only if legal review finishes by May 14 and analytics instrumentation is approved this week. The workstream at highest risk is customer migration messaging, which still lacks final segmentation criteria.
```

---

## 4) Weekly Reviews

### Prompt 16: Personal Weekly Review

**Use when:** You want a sharper end-of-week review than "what got done?"

```text
Act as an executive coach with strong operating instincts.

Help me run a weekly review based on the material below.

Inputs:
- Calendar summary:
- Task list summary:
- Notes from the week:
- Wins:
- Frustrations:

Instructions:
- Identify the 3 outcomes that mattered most.
- Distinguish output from impact.
- Surface recurring friction.
- Recommend what to stop, continue, and start next week.

Output:
1. Weekly review summary
2. Lessons learned
3. Priority list for next week
```

### Prompt 17: Team Weekly Operating Review

**Use when:** You need a leader-friendly summary of the team’s week.

```text
Create a team weekly operating review.

Context:
- Team:
- Main goals:
- Reporting period:

Inputs:
[paste notes, updates, metrics, blockers]

Instructions:
- Group updates by outcome, not person.
- Highlight where momentum increased or decreased.
- Pull out blockers that need escalation.
- Keep the writing concise and decision-friendly.

Output:
1. Weekly operating review
2. Escalations required
3. Top 3 priorities for next week
```

### Prompt 18: Goal Drift Detector

**Use when:** You feel busy but are not sure the work is aligned.

```text
Review the information below and tell me where my work may be drifting away from priorities.

Priority goals:
[paste goals]

What I actually spent time on:
[paste calendar/tasks/notes]

Instructions:
- Compare time spent to stated priorities.
- Identify drift patterns.
- Separate urgent noise from strategic work.
- Recommend specific corrections for next week.

Output:
1. Drift analysis
2. What to cut
3. What to protect
4. A better weekly plan
```

### Prompt 19: Energy and Time Audit

**Use when:** Work is getting done but at an unsustainable cost.

```text
Analyze my week for energy drains, context switching, and time waste.

Inputs:
[paste schedule, tasks, notes, feelings, interruptions]

Instructions:
- Look for patterns that repeatedly consume attention.
- Distinguish necessary work from avoidable drag.
- Suggest operational fixes, not just mindset advice.
- Prioritize changes by likely impact.

Output:
1. Time/energy audit
2. Top 5 fixes
3. A redesigned ideal week
```

### Prompt 20: Leadership Weekly Digest

**Use when:** You need to send a polished leadership summary every Friday.

```text
Draft a leadership weekly digest from the information below.

Audience:
- Seniority:
- What they care about most:

Inputs:
[paste notes]

Instructions:
- Start with the biggest headline.
- Include wins, risks, and asks.
- Keep the tone sober and useful.
- End with what leadership should watch next week.

Output:
1. Final digest
2. Slack-friendly shorter version
```

**Example output snippet**

```text
Biggest headline: Pipeline cleanup is improving conversion quality, but it is temporarily masking top-of-funnel softness. We should treat this as a quality gain, not true demand growth, until next week's cohort data confirms the trend.
```

---

## 5) Hiring

### Prompt 21: Hiring Scorecard Builder

**Use when:** A role is fuzzy and interviews risk becoming subjective.

```text
Build a hiring scorecard for this role.

Role details:
- Title:
- Team:
- Core outcomes expected in the first 12 months:
- Must-have skills:
- Nice-to-have skills:
- Known failure modes:

Instructions:
- Convert the role into 5-7 scorecard dimensions.
- Define what strong, mixed, and weak evidence looks like for each.
- Keep criteria observable.

Output:
1. Scorecard table
2. Top 3 interview themes
3. Risks if we hire too junior or too senior
```

### Prompt 22: Job Description Rewriter

**Use when:** A job description sounds generic or overloaded.

```text
Rewrite this job description so that strong candidates self-select in.

Current job description:
[paste JD]

Instructions:
- Clarify the actual mission of the role.
- Replace vague buzzwords with concrete responsibilities.
- Make the first 90-day expectations visible.
- Remove unrealistic wish-list language.
- Keep the tone sharp and credible.

Output:
1. Rewritten job description
2. A shorter version for LinkedIn
3. Three lines that make the role more compelling
```

### Prompt 23: Structured Interview Question Set

**Use when:** You want better evidence than unstructured conversation.

```text
Create a structured interview question set for this role.

Role context:
[paste role context]

Instructions:
- Generate behavioral and situational questions.
- Tie each question to a scorecard dimension.
- Include follow-up probes.
- Avoid trivia or gotcha questions.

Output:
For each question include:
- Question
- What strong evidence sounds like
- What weak evidence sounds like
- Follow-up probe
```

### Prompt 24: Candidate Debrief Synthesizer

**Use when:** Several interviewers have scattered notes and you need a clear recommendation.

```text
Synthesize the candidate feedback below into a hiring recommendation.

Inputs:
[paste interviewer notes]

Instructions:
- Group evidence by scorecard dimension.
- Separate signal from opinion.
- Call out contradictions between interviewers.
- Make a recommendation: strong yes / yes / mixed / no.
- Explain what evidence is missing.

Output:
1. Debrief summary
2. Recommendation and rationale
3. Follow-up interview gaps, if any
```

### Prompt 25: Reference Check Planner

**Use when:** You want references to produce real signal instead of polite anecdotes.

```text
Create a focused reference check plan for this candidate.

Role:
[paste role context]

Candidate profile:
[paste summary]

Instructions:
- Identify the biggest open risks.
- Turn each risk into a direct but professional reference question.
- Include follow-up probes.
- Add a short intro and close for the call.

Output:
1. Reference check plan
2. 8-10 questions
3. Red flags to listen for
```

---

## 6) Delegation

### Prompt 26: Delegation Brief Writer

**Use when:** You know what needs doing, but the handoff is still fuzzy.

```text
Turn my rough notes into a clean delegation brief.

Task or project:
- Goal:
- Owner:
- Why this matters:
- Deadline:
- Constraints:
- Success criteria:

Notes:
[paste notes]

Instructions:
- Clarify the desired outcome.
- Distinguish requirements from suggestions.
- Identify likely ambiguities up front.
- Make the brief easy for a busy teammate to act on.

Output:
1. Delegation brief
2. Checklist of what the owner should confirm back
```

### Prompt 27: Handoff Package Generator

**Use when:** Work is moving from one owner to another and context could get lost.

```text
Create a handoff package from the information below.

Context:
- Workstream:
- Current owner:
- New owner:
- Deadline or phase:

Source material:
[paste docs, notes, links, status, risks]

Instructions:
- Summarize current status first.
- List what is done, in progress, blocked, and next.
- Surface hidden context, stakeholder sensitivities, and risks.
- End with the exact first actions for the new owner.

Output:
1. Handoff summary
2. Risk list
3. First-week action plan
```

### Prompt 28: Review Delegated Work

**Use when:** You want to give useful feedback on delegated work without rewriting it yourself.

```text
Review the work below and help me give feedback that improves it without taking ownership back.

Assigned objective:
[paste objective]

Submitted work:
[paste work]

Instructions:
- Evaluate against the original objective.
- Identify what is strong, weak, and unclear.
- Suggest improvements in order of impact.
- Keep the tone developmental and accountable.

Output:
1. Internal evaluation
2. Feedback message to send
3. Questions to ask before approving
```

### Prompt 29: Escalation Decision Helper

**Use when:** You are unsure whether to step in, coach, or escalate a delegation issue.

```text
Help me decide how to respond to a delegation problem.

Situation:
- What was delegated:
- What happened:
- Business impact:
- Time sensitivity:
- Capability issue, clarity issue, or ownership issue?:

Instructions:
- Diagnose the likely root cause.
- Recommend one of: clarify, coach, step in, reassign, escalate.
- Explain the tradeoff of each option.
- Draft the message I should send.

Output:
1. Recommended path
2. Why
3. Draft message
```

### Prompt 30: Accountability Check-In

**Use when:** You want a concise follow-up that drives progress without micromanaging.

```text
Write an accountability check-in message for the task below.

Context:
- Person:
- Task:
- Deadline:
- Current status:
- Tone:

Instructions:
- Keep it respectful and direct.
- Ask for the specific update that matters.
- Reinforce the expected outcome and timing.
- Avoid vague "just checking in" wording.

Output:
1. Slack version
2. Email version
```

**Example output snippet**

```text
Can you send me the current state of the launch checklist by 3 PM, including anything that is blocked or likely to slip? I want to make sure we resolve issues before tomorrow's review, not during it.
```

---

## 7) SOPs

### Prompt 31: SOP Draft From Expert Notes

**Use when:** You have subject-matter knowledge but not a documented process.

```text
Turn the notes below into a usable SOP.

Process name:
- Purpose:
- Trigger:
- Owner:
- Frequency:

Notes:
[paste steps, screenshots text, rough bullets, tribal knowledge]

Instructions:
- Write the SOP for a competent new team member.
- Use numbered steps.
- Include required inputs, tools, and decision points.
- Add a final QA checklist.
- Keep language practical, not academic.

Output:
1. SOP
2. Common failure points
3. QA checklist
```

### Prompt 32: SOP Gap Analysis

**Use when:** An existing SOP feels incomplete, brittle, or too expert-dependent.

```text
Audit this SOP for clarity, completeness, and risk.

Current SOP:
[paste SOP]

Instructions:
- Identify missing steps, hidden assumptions, and unclear wording.
- Flag where a new team member would fail.
- Recommend what to add, simplify, or reorder.
- Suggest measurements that show the SOP is working.

Output:
1. Gap analysis
2. Revised SOP outline
3. Risk controls to add
```

### Prompt 33: QA Checklist Generator

**Use when:** A repeatable process needs a final quality gate.

```text
Create a QA checklist for this workflow.

Workflow:
[describe workflow]

Known failure modes:
[paste failure modes]

Instructions:
- Focus on the checks that prevent high-cost mistakes.
- Group checks by phase: before, during, after.
- Keep each checklist item observable and binary where possible.

Output:
1. QA checklist
2. Top 5 critical checks
3. Suggested owner for sign-off
```

### Prompt 34: Training Guide From SOP

**Use when:** You need to turn a process into a teachable onboarding artifact.

```text
Convert this SOP into a short training guide for a new hire.

SOP:
[paste SOP]

Instructions:
- Explain the purpose of the process first.
- Translate jargon into plain language.
- Highlight the mistakes new people are most likely to make.
- Include a quick practice exercise and answer key.

Output:
1. Training guide
2. 10-minute walkthrough agenda
3. Practice exercise
```

### Prompt 35: Postmortem to SOP Update

**Use when:** An incident happened and you want process improvement, not just a retrospective.

```text
Turn this incident/postmortem into SOP updates.

Incident summary:
[paste summary]

Current SOP if available:
[paste SOP]

Instructions:
- Identify which control failed or was missing.
- Recommend changes to the SOP, checklist, and training.
- Distinguish immediate patch fixes from durable process changes.
- Keep the recommendations practical.

Output:
1. SOP changes to make
2. Updated checklist items
3. Training or communication changes
4. Owner and timeline recommendations
```

**Example output snippet**

```text
Immediate patch: Add a required peer review before customer-facing exports are sent.

Durable process change: Update the SOP so the export owner must validate field mappings against the latest schema version, not the last successful run.
```

---

## Bonus: Fast Prompt Refiners

Use these after any first draft:

- "Tighten this by 25% without losing meaning."
- "Make this sound more decisive and less padded."
- "Turn this into a version for an executive who only has 30 seconds."
- "What is unclear, risky, or likely to be challenged in this draft?"
- "Rewrite this for Slack while preserving the core message."

## Final Advice

The value of AI at work is rarely in one perfect prompt. It comes from combining:

- real context
- a clear desired output
- strong judgment about what to keep, cut, and verify

Use this pack to shorten the distance between rough thinking and useful execution.

If you use these prompts consistently, you should see immediate gains in speed, clarity, and follow-through.