10 battle-tested, copy-ready prompt templates covering the most common professional use cases. Click any template to copy it — just fill in the [BRACKETS] and go.
You are a senior project manager. I am kicking off a project called [PROJECT NAME] at [COMPANY NAME]. The primary goal is [ONE-SENTENCE GOAL]. Key stakeholders are [STAKEHOLDER LIST]. Timeline is [START DATE] to [END DATE].
Draft a project kickoff document that includes: (1) executive summary, (2) scope and out-of-scope items, (3) key milestones with dates, (4) RACI matrix for the top 5 workstreams, (5) risk register with likelihood and impact ratings, and (6) a "definition of done" for the final deliverable.
Format with clear headers. Be specific — avoid generic filler.
Why it works: Providing role context ("senior project manager") activates domain-specific vocabulary and structure. Enumerating the exact outputs removes ambiguity and prevents the model from producing a generic response. The final instruction "avoid generic filler" directly suppresses boilerplate.
02Status Update Prompts
Template
You are a concise executive communicator. I need a weekly status update email for the project "[PROJECT NAME]" addressed to [AUDIENCE, e.g. VP of Engineering].
Raw notes from this week:
[PASTE YOUR BULLET NOTES HERE]
Transform the notes into a structured status update with these sections:
- Overall status: [Green / Yellow / Red] — one sentence why
- Accomplishments this week (3-5 bullets, past tense, outcome-focused)
- Blockers and risks (with owner and due date for each)
- Next week's priorities (3-5 bullets)
- Asks from recipient (if any)
Keep the total email under 250 words. No greetings or sign-offs needed.
Why it works: The word-count constraint forces concision. Separating raw notes from the output format lets you dump thoughts freely while still getting polished output. Specifying past tense for accomplishments and asking for owners on blockers produces actionable, not decorative, updates.
03Code Review Prompts
Template
You are a staff-level software engineer at a [LANGUAGE, e.g. Python] shop. Review the following code diff for a [CONTEXT, e.g. REST API endpoint that processes payments].
```
[PASTE CODE DIFF OR SNIPPET HERE]
```
Produce a structured code review covering:
1. **Correctness** — logic bugs, edge cases, or incorrect assumptions
2. **Security** — injection risks, auth gaps, secrets in code, insecure defaults
3. **Performance** — O(n) bottlenecks, N+1 queries, unnecessary allocations
4. **Readability** — naming, comment quality, over-complexity
5. **Suggested rewrites** — for any critical issues, provide a corrected snippet
Rate each category: LGTM / Minor / Major / Blocker. Prioritize Blockers at the top.
Why it works: A structured taxonomy (correctness, security, performance, readability) prevents the model from focusing only on style. Asking for severity ratings (LGTM to Blocker) mimics real code review tooling and makes it easy to triage. Requesting corrected snippets for blockers turns feedback into immediate action.
04Meeting Summary Prompts
Template
You are a highly organized executive assistant. Below is a raw transcript (or notes) from a [MEETING TYPE, e.g. product roadmap review] attended by [ATTENDEE ROLES, e.g. CEO, CPO, two engineering leads] on [DATE].
Transcript:
[PASTE TRANSCRIPT OR NOTES]
Produce a clean meeting summary with:
- **One-paragraph TL;DR** (3-4 sentences, decision-focused)
- **Key decisions made** (each with owner if mentioned)
- **Action items** (format: [Owner] will [action] by [date])
- **Open questions** that were raised but not resolved
- **Parking lot** items deferred to a future meeting
Do not include filler phrases. If a field has no content, write "None noted."
Why it works: The [Owner] will [action] by [date] format enforces accountability rather than vague "we should" action items. Explicitly asking for open questions and a parking lot captures the dark matter of meetings — the unresolved stuff that causes follow-up confusion.
05Email Drafting Prompts
Template
You are a professional business writer. Draft an email with the following parameters:
- **From:** [YOUR NAME AND TITLE]
- **To:** [RECIPIENT NAME AND RELATIONSHIP, e.g. a vendor we've worked with for 2 years]
- **Purpose:** [CORE GOAL, e.g. decline a contract renewal while keeping the relationship intact]
- **Tone:** [TONE, e.g. warm but firm]
- **Key points to include:** [LIST YOUR KEY POINTS]
- **What to avoid:** [e.g. blame language, vague commitments, excessive apology]
Write the email in full. Subject line first, then body. Keep it under [WORD COUNT, e.g. 150] words. End with a clear next step or call-to-action.
Why it works: The "what to avoid" field is underused but powerful — it prevents the model from defaulting to overused phrasings like "I hope this email finds you well." Specifying relationship context shifts the tone automatically. A hard word count prevents padding.
06Competitive Analysis Prompts
Template
You are a market intelligence analyst. I am a product manager at [YOUR COMPANY] working on [YOUR PRODUCT / FEATURE] in the [MARKET / INDUSTRY] space.
Compare us against the following competitors: [COMPETITOR 1], [COMPETITOR 2], [COMPETITOR 3].
Produce a competitive analysis with:
1. **Comparison matrix** — rows: key buying criteria ([LIST 5-7 CRITERIA]); columns: us + each competitor. Rate each cell: Strong / Adequate / Weak.
2. **Their likely positioning against us** — one paragraph per competitor
3. **Our differentiation opportunities** — where we can legitimately claim superiority
4. **Threats to watch** — capabilities they are building that could close our gaps
Base your analysis on publicly known information. Flag any assumptions clearly.
Why it works: Asking for a matrix with explicit criteria forces structured thinking rather than narrative hand-waving. The "flag assumptions" instruction prevents the model from presenting guesses as facts — critical for competitive work. Separating "differentiation" from "threats" gives both an offensive and defensive view.
07Job Description Prompts
Template
You are a talent acquisition specialist and organizational psychologist. Write a job description for a [JOB TITLE] role at [COMPANY NAME], a [COMPANY DESCRIPTION, e.g. Series B SaaS startup building AI tools for finance teams].
Requirements:
- The candidate must have: [HARD REQUIREMENTS]
- Nice to have: [PREFERRED SKILLS]
- This person will report to: [MANAGER TITLE]
- Team size: [NUMBER] people
Format the JD with: (1) a compelling 2-sentence company hook, (2) "What you'll do" — 5-7 outcome-focused bullets, (3) "What you'll bring" — separated into Must-Have and Nice-to-Have, (4) "Why join us" — 3 bullets on culture/impact/growth, (5) compensation range if provided: [RANGE OR "omit"].
Use active language. Avoid jargon like "rockstar," "ninja," or "passionate."
Why it works: Outcome-focused bullets ("you will ship X" vs. "responsible for X") attract candidates who think in results. Explicitly separating must-have from nice-to-have prevents self-selection bias where qualified candidates don't apply. Banning clichés like "rockstar" keeps the tone credible.
08Customer Feedback Analysis Prompts
Template
You are a UX researcher and product analyst. I have collected [NUMBER] pieces of customer feedback for [PRODUCT NAME]. The feedback comes from [SOURCE, e.g. NPS survey, app store reviews, support tickets].
Raw feedback:
[PASTE FEEDBACK HERE — can be CSV rows, raw text, or bullet list]
Analyze the feedback and produce:
1. **Sentiment breakdown** — estimated % positive / neutral / negative with 1-line rationale
2. **Top 5 themes** — each with a label, frequency estimate, and 2-3 verbatim examples
3. **Quick wins** — issues mentioned by multiple users that appear low-effort to fix
4. **Feature requests ranked by frequency**
5. **Red flags** — any feedback suggesting churn risk, legal/compliance concern, or reputational issue
Close with a one-paragraph executive summary suitable for a product review meeting.
Why it works: Asking for verbatim examples anchors theme labels in actual customer language, preventing the analyst (or the model) from paraphrasing away signal. The "red flags" category surfaces issues that pure sentiment scoring misses. The executive summary forces synthesis rather than leaving it as raw data.
09Budget Justification Prompts
Template
You are a finance-savvy business writer. I need to justify a budget request of [DOLLAR AMOUNT] for [INITIATIVE NAME] to [APPROVER TITLE, e.g. CFO].
Context:
- Current situation / problem: [DESCRIBE THE PROBLEM OR OPPORTUNITY]
- What the budget will fund: [LIST SPEND ITEMS]
- Expected outcomes: [MEASURABLE RESULTS]
- Timeline to ROI: [TIMEFRAME]
- Cost of inaction: [WHAT HAPPENS IF WE DON'T DO THIS]
Write a one-page budget justification memo with: (1) executive summary, (2) problem statement with supporting data if provided, (3) proposed solution and line-item budget breakdown, (4) ROI calculation or qualitative benefit if hard ROI is not measurable, (5) risk of inaction, (6) recommended decision and timeline.
Tone: direct and numbers-first. Avoid marketing language.
Why it works: "Cost of inaction" is the most persuasive framing in budget approval — it reframes the ask from an expense to a risk mitigation. Providing the line-item breakdown as input gives the model real numbers to work with instead of fabricating plausible-sounding ones. "Numbers-first" tone instruction prevents fluffy corporate prose.
10Strategic Planning Prompts
Template
You are a strategy consultant with experience in [INDUSTRY]. I am the [YOUR TITLE] of [COMPANY NAME], a [COMPANY DESCRIPTION].
We are planning for [PLANNING HORIZON, e.g. FY2027]. Our current state:
- Revenue: [CURRENT ARR OR REVENUE]
- Team size: [NUMBER]
- Top strength: [ONE SENTENCE]
- Top weakness: [ONE SENTENCE]
- Biggest external opportunity: [ONE SENTENCE]
- Biggest external threat: [ONE SENTENCE]
Produce a strategic plan outline with:
1. **Vision for end of planning period** — one sentence
2. **3 strategic bets** — each with hypothesis, key actions, success metrics, and resource requirements
3. **What we are choosing NOT to do** — explicit anti-goals to prevent scope creep
4. **Leading indicators to track quarterly**
5. **Scenario planning** — brief take on best case / base case / downside case
Be opinionated. Do not hedge every statement. If the inputs suggest a pivot, say so.
Why it works: "What we are choosing NOT to do" is the most underused strategy tool — it forces prioritization. Asking the model to "be opinionated" and "not hedge" overrides the default tendency to produce balanced, non-committal output. Scenario planning in a single prompt gives you the optionality analysis that usually requires a separate workshop.
Want Better Results From Every Prompt?
Grade any prompt instantly with our free tool, or get the full 50-prompt pack used by product managers at fast-moving teams.