Prompt library

How to ask, what to try, and example prompts from real PM work — genericized. I’m still organizing this; for now, everything lives here.

How to write a good prompt

  • Be clear — spell out exactly what you want
  • Add purpose — who is the audience? why do you need this?
  • Shape the output — table, bullets, email, one page, etc.
Summarize this project status report into 3 executive-level bullet points for senior leadership. Use plain, non-technical language. Format as a table with columns: Key Point and Business Impact.

Stuck on how to ask? Try:

Tell me how to write a prompt if I need to [describe your challenge or desired outcome].

Example prompts by use case

Typical pattern: 10–15 AI assists per day, meaningful hours reclaimed for strategy and people.

Consolidating risks, issues, and dependencies

Project health check across multiple status decks.

Based on these PowerPoint documents, provide a consolidated list of Risks, Issues, and Dependencies. Put the data into Excel format.

Typical time saved: ~8 hours vs. manual slide-by-slide extraction

Risk prioritization and scoring

Objective scores for stakeholder discussions.

Evaluate each item and assign a criticality score from 1 to 20. For each item, explain why — consider timeline sensitivity, impact on project success, and resource requirements.

Typical time saved: ~6 hours

Timeline from meetings and messages

Quick turnaround visual for leadership.

Create a table of activities and milestones with dates, notes, and duration. Use available meetings, emails, and chat messages. Organize chronologically.

Typical time saved: ~8 hours → often under 30 minutes with edits

Meeting notes → action items

Structured output for trackers and follow-up.

Very succinct, actionable summary. Key takeaways and next steps with owners for each topic. One table organized by workstream or key topic.

Typical manual cleanup: 30–45 minutes per meeting

Executive summary

Leadership-ready language, not raw notes.

Executive summary with no more than 3 bullets. By topic: one bullet for an impactful takeaway and one for next steps.

Testing checklist from user stories

Release prep across scenarios and acceptance criteria.

Based on the user stories and descriptions in the attached file, create a detailed testing checklist.

Typical time saved: ~4–6 hours

Project health check framework

Structured review before a deep dive.

I'm reviewing a project and want a health check. What key areas should I review (scope, schedule, budget, risks, stakeholders, governance, etc.)? For each area, outline best practices and specific questions I should ask.

Typical time saved: ~5–7 hours of framework research

High-level plan from backlog export

Phases and milestones when agile work needs a timeline view.

Based on this export of user stories, suggest a high-level project plan with phases, milestones, and dates. Put the output in Excel format.

Typical time saved: ~4 hours

Clean exported descriptions

HTML markup stripped from spreadsheet columns.

Remove all HTML and markup in the Description column please.

Typical time saved: ~20 minutes of find-and-replace

Tool comparison

Structured evaluation for a selection decision.

Compare popular roadmap tools across core features, collaboration, integrations, ease of use, governance, pricing, and best-fit use cases. Comparison table plus short summary.

Typical time saved: ~8–10 hours of research

Status meeting talking points

Short scripts so updates stay within time.

Create script and talking points for this slide. Match my usual style. No longer than 3 minutes to present.

Starter prompt patterns

Weekly status report

Clear: Summarize the project update.
Purpose: Executives who need a high-level view.
Output: One page with headings: Progress, Risks, Next Steps.

Risk log

Clear: Organize this list of risks.
Purpose: Team prioritization.
Output: Table with Impact, Likelihood, Mitigation.

Stakeholder update

Clear: Draft a short project update.
Purpose: Non-technical stakeholders.
Output: Email, 3 concise paragraphs.

Lessons learned

Clear: Analyze these project notes for insights.
Purpose: Improve future projects.
Output: 3 bullets under “Lessons Learned.”

Iterate

First outputs aren’t final. “Shorter.” “Put action items in a table with owners.” “Plain language.” The value is in the back-and-forth — with you still in charge.

Every example assumes approved tools, sanitized inputs, and a human review before anything is shared. See guardrails and the full presentation.