AI Prompt Library

I'm going to paste my meeting notes below. Please analyze them and return:

1. **Meeting Summary** (2-3 sentences)
2. **Key Decisions Made** (bulleted list)
3. **Action Items** — formatted as a table with columns: Action Item | Owner | Deadline | Priority (High/Medium/Low)
4. **Open Questions** — anything unresolved that needs follow-up

If no deadline was mentioned for an action item, flag it as "TBD — needs date."

Here are my meeting notes:
[PASTE NOTES HERE]

I'm going to paste a list of emails (subject lines and brief descriptions). For each one, categorize it into:

- 🔴 **Urgent** — Needs response today
- 🟡 **This Week** — Important but not time-sensitive
- 🟢 **Low Priority** — Can wait or delegate
- 🗑️ **Skip** — No action needed

For each email, also add a suggested one-line response or action. Format as a table.

Here are my emails:
[PASTE EMAIL LIST HERE]

I'm going to paste a vendor pitch, marketing email, or product description. Please:

1. **Plain-English Summary** — What does this product actually do? (3-4 sentences, no jargon)
2. **What They're Really Saying** — Translate each buzzword or vague claim into what it practically means
3. **Questions to Ask** — 3-5 questions I should ask the vendor before buying
4. **Red Flags** — Any vague claims, missing details, or things that sound too good

Here's the text:
[PASTE VENDOR PITCH HERE]

Turn my rough notes into a professional weekly status report. Use this format:

**Status Report — [Week of DATE]**

**Completed This Week:**
- (Accomplishments with brief context on impact)

**In Progress:**
- (What's actively being worked on + expected completion)

**Blocked / Needs Attention:**
- (Anything stuck, with who/what is needed to unblock)

**Next Week's Priorities:**
- (Top 3-5 planned items)

Keep the tone professional but human — not robotic. Here are my rough notes:
[PASTE BULLET POINTS HERE]

I'm going to paste a company policy document. Please create a TL;DR summary with:

1. **One-Paragraph Summary** — What this policy is about and why it exists
2. **Key Rules** — The 5-7 most important rules/requirements, in plain language
3. **What Changed** — If this appears to be an update, highlight what's new or different
4. **Who This Affects** — Which roles or teams need to pay attention
5. **Action Required** — Specific things employees need to do (with any deadlines)
6. **Common Scenarios** — 3 practical "Can I...?" examples with yes/no answers

Write for someone who has 2 minutes to understand this policy.

Here's the document:
[PASTE POLICY TEXT HERE]

Help me write a post-mortem for a recent incident. I'll describe what happened, and you create a structured document with:

1. **Incident Summary** — What happened, when, and who was impacted
2. **Timeline** — Chronological events from detection to resolution (use table format)
3. **Root Cause** — What actually caused the issue (ask me clarifying questions if needed)
4. **Impact** — Users affected, duration, any data/revenue impact
5. **What Went Well** — Things that worked during the response
6. **What Went Wrong** — Gaps in process, tooling, or communication
7. **Action Items** — Preventive measures with owners and due dates (table format)
8. **Severity Rating** — Suggest a severity level (SEV 1-4) with justification

Here's what happened:
[DESCRIBE THE INCIDENT]

I'm going to describe a process that currently lives in someone's head. Turn it into a structured runbook with:

**Runbook: [Process Name]**

- **Purpose:** Why and when to use this runbook
- **Prerequisites:** Access, tools, or permissions needed before starting
- **Estimated Time:** How long this typically takes

**Steps:**
(Numbered steps with enough detail that someone unfamiliar could follow them. Include exact commands, URLs, or file paths where relevant.)

**Troubleshooting:**
(Common issues and how to resolve them — "If you see X, do Y")

**Escalation:**
(When to escalate and who to contact)

**Last Updated:** [Today's date]

Here's the process I want to document:
[DESCRIBE THE PROCESS]

I need to submit a change request. I'll describe what I want to do in plain language, and you generate a formal change request with:

1. **Change Title** — Clear, descriptive title
2. **Change Description** — What is being changed and why
3. **Business Justification** — Why this change is needed
4. **Scope & Impact** — Systems, users, and services affected
5. **Risk Assessment** — Low/Medium/High with justification
6. **Rollback Plan** — How to undo this change if something goes wrong
7. **Testing Plan** — How we'll verify the change works
8. **Implementation Steps** — Ordered list of what will happen during the change window
9. **Communication Plan** — Who needs to be notified before, during, and after
10. **Requested Window** — Suggested timing and duration

Here's what I want to do:
[DESCRIBE YOUR CHANGE]

I need to compare vendors/tools for a decision. Help me build a comparison matrix.

First, I'll tell you:
- **What I'm evaluating:** [e.g., project management tools]
- **The options:** [e.g., Jira, Asana, Linear, Monday.com]
- **My must-haves:** [e.g., SSO, API access, under $15/user/mo]
- **Nice-to-haves:** [e.g., time tracking, custom fields]

Please create:
1. **Comparison Table** — Rows = criteria, Columns = vendors. Use ✅/❌/⚠️ for feature support
2. **Pricing Breakdown** — Cost per user at my team size
3. **Pros & Cons** — Top 3 of each per vendor
4. **Recommendation** — Your suggested pick with reasoning
5. **Questions to Ask Each Vendor** — Before signing

Here are my details:
[FILL IN THE DETAILS ABOVE]

Generate a structured onboarding checklist for a new hire. I'll provide the role/job description and you create:

**Week 1: Foundations**
- Day 1: (Orientation, access setup, key introductions)
- Day 2-3: (Core tools, reading material, shadow sessions)
- Day 4-5: (First small tasks, team norms, 1:1 with manager)

**Week 2: Building Context**
- (Deeper tool training, process walkthroughs, key stakeholder meetings)

**Week 3-4: Contributing**
- (First real assignments, feedback checkpoints, independence milestones)

**30-60-90 Day Goals:**
- 30 days: (Expected competencies)
- 60 days: (Contributing independently)
- 90 days: (Fully ramped outcomes)

**Access & Tools Needed:** (Checklist of accounts/tools to provision on day 1)

Here's the role:
[PASTE JOB DESCRIPTION OR DESCRIBE THE ROLE]

I need to send a status update to non-technical stakeholders. I'll give you the technical details, and you rewrite it as an executive-friendly update.

Rules:
- No jargon or acronyms without explanation
- Lead with business impact, not technical details
- Use concrete numbers where possible
- Keep it under 200 words
- End with clear next steps or asks

Format:
**Subject:** [Clear, outcome-focused subject line]

**Bottom Line:** (1-2 sentences — what they need to know)

**Details:** (3-4 bullet points, plain language)

**Next Steps:** (What's happening next + any decisions needed from them)

Here are the technical details:
[PASTE YOUR TECHNICAL UPDATE]

I need to deliver bad news professionally. Help me draft a message that:

1. Leads with the key information (don't bury the bad news)
2. Explains what happened and why (briefly, no excuses)
3. Shows what we're doing about it (concrete actions)
4. Provides a realistic timeline for resolution
5. Ends with next steps and how to reach me for questions

Tone: Direct, empathetic, professional. Not overly apologetic or defensive.

Details:
- **Who is this going to?** [e.g., my team, leadership, a client]
- **What's the bad news?** [e.g., project delayed 3 weeks, budget cut 20%, system outage]
- **Why did it happen?** [brief explanation]
- **What are we doing about it?** [any mitigation or next steps]

[FILL IN THE DETAILS ABOVE]

I need to escalate an issue that's stuck. Help me write an email that's firm but professional.

The email should:
1. Clearly state what's blocked and since when
2. Summarize what's already been tried
3. Explain the business impact of continued delay
4. Make a specific ask (what I need and by when)
5. Keep the tone constructive — not blaming, but urgent

Format:
**Subject:** [Action Needed] — [Brief description of blocked item]

**Body:** (Professional escalation following the structure above, under 250 words)

Here's my situation:
- **What's stuck:** [describe the issue]
- **How long it's been stuck:** [timeline]
- **What I've already tried:** [previous attempts to resolve]
- **Who I'm escalating to:** [role/name]
- **Business impact:** [what happens if this stays stuck]

[FILL IN THE DETAILS ABOVE]

I have technical documentation that's accurate but painful to read. Rewrite it so humans actually want to read it.

Rules:
- Keep all technical accuracy — don't dumb it down, make it clearer
- Use short sentences and active voice
- Add brief "why this matters" context where helpful
- Use headers, bullets, and formatting for scannability
- Include practical examples where the original is abstract
- If there are steps, number them and make each one a clear action
- Tone: Knowledgeable colleague, not a textbook

Don't add information that isn't in the original — just make what's there more readable.

Here's the documentation to rewrite:
[PASTE DOCUMENTATION HERE]

I have feedback that's honest but might come across too harsh. Rewrite it to be constructive and actionable while keeping the core message intact.

For each piece of feedback, give me:
1. **Original intent** — What I'm really trying to say
2. **Rewritten version** — Professional, constructive phrasing
3. **Suggested format** — Whether this is best delivered in writing, in a 1:1, or in a group setting

Rules:
- Keep the honesty — don't water it down to meaninglessness
- Focus on behavior/output, not the person
- Include a specific suggestion for improvement
- Use "I noticed..." or "Going forward..." framing where appropriate

Here's my blunt feedback:
[PASTE YOUR FEEDBACK HERE]