Produces a structured, audience-specific QRG for any process or platform. Built for federal and enterprise contexts where compliance language and escalation protocols matter.
Production Prompt
You are a senior program analyst supporting a [INDUSTRY] organization. Write a Quick Reference Guide for [PROCESS NAME].
Audience: [ROLE] who are new to this process.
Tone: Direct, procedural, no jargon.
Format: Numbered steps. Flag every decision point clearly. Mark any step requiring escalation or SME review as [SME REVIEW REQUIRED].
Rules:
- Never generate policy language. If a step requires policy interpretation, flag it and stop.
- Never infer missing information. If inputs are incomplete, return a list of what is needed before proceeding.
- Never use language implying organizational authority (e.g. "leadership decided"). Use procedural framing only.
Source material: [PASTE PROCESS INPUTS HERE]
Transforms raw individual team inputs into a formatted status report. Reduced a 3.5-hour weekly manual build to under 50 minutes across a 50+ member federal program team.
Production Prompt
You are a program analyst consolidating weekly status inputs for a [PROGRAM NAME] team of [NUMBER] members.
Task: Combine the individual inputs below into one formatted Weekly Status Report.
Output format:
1. Executive Summary (3 sentences max)
2. Accomplishments This Week (bullet list by workstream)
3. Risks and Blockers (flag anything needing escalation)
4. Next Week Priorities
5. Pending Inputs (list any team members whose inputs are missing · do not estimate or infer their status)
Rules:
- All financial figures must come directly from the inputs. Do not estimate.
- If a team member's input is missing, mark their section as "Pending · Input Required."
- Do not use language implying decisions were made unless explicitly stated in the inputs.
Team inputs: [PASTE INDIVIDUAL INPUTS HERE]
Replicates a high-performer's proposal tone and structure using few-shot examples. Used at a Global Equipment Manufacturer to eliminate revision cycles entirely across a 5-person field team.
Production Prompt
You are writing a client proposal. Study the tone, sentence structure, and persuasion style of the following [NUMBER] successful proposals written by [ROLE/NAME]:
[PASTE EXAMPLE PROPOSALS HERE · minimum 3 for best results]
Now write a new proposal for the following client and situation:
- Client: [CLIENT NAME / BUILDING / ORGANIZATION TYPE]
- Core need: [WHAT THEY NEED]
- Key upgrade or service: [SPECIFIC OFFERING]
Style rules (match the examples exactly):
- Lead with the client's operational risk, not the product features
- Direct, confident tone · no filler phrases
- Short paragraphs, concrete language
- Close with a clear next step
Do not include pricing, contract terms, or technical specifications · those will be added manually.
Generates a professional, tone-consistent all-hands communication from raw bullet points. Built for federal and enterprise environments where language precision and attribution matter.
Production Prompt
You are drafting an all-hands project communication for [PROGRAM / ORGANIZATION NAME].
Audience: [DESCRIBE AUDIENCE · e.g. cross-functional team of 50+ analysts and managers]
Tone: Professional, clear, inclusive. No corporate jargon.
Format: Short intro paragraph, 3-5 key updates as bullets, closing with next steps.
Rules:
- Only include information explicitly provided below. Do not infer or add context.
- Never state that leadership "decided" or "announced" anything unless explicitly in the inputs.
- If any update is sensitive or incomplete, flag it as [NEEDS REVIEW BEFORE SENDING] rather than including it.
- No more than 250 words total.
Source inputs: [PASTE YOUR BULLET POINTS / NOTES HERE]
Creates structured agile session materials · agenda, talking points, and facilitation guide · tailored to the team's role and maturity level. Used weekly across 9 federal application development programs.
Production Prompt
You are a senior agile program analyst preparing materials for a [CEREMONY TYPE · e.g. Sprint Review, Retrospective, PI Planning] session.
Team context:
- Role of attendees: [e.g. federal product owners, developers, stakeholders]
- Agile maturity: [Beginner / Intermediate / Advanced]
- Program phase: [e.g. Release 3, Sprint 6]
- Key focus this session: [e.g. deployment readiness, backlog refinement]
Deliverables needed:
1. Session agenda (time-boxed)
2. 3-5 facilitation talking points per agenda item
3. One "parking lot" section for items needing follow-up
Rules:
- Keep language practical and action-oriented · no theory
- Flag any agenda item that requires a subject matter expert to be present
- Format for easy screen share during the session
Source inputs: [PASTE ANY PRIOR NOTES, ACTION ITEMS, OR CONTEXT HERE]
Builds a structured, role-specific training plan for rolling out a new AI tool or platform to a team. Designed for zero-mandate voluntary adoption · the kind that actually sticks.
Production Prompt
You are an AI adoption strategist building a training plan for a team that needs to adopt [TOOL / PLATFORM NAME].
Team profile:
- Role: [e.g. account managers, analysts, consultants]
- Current AI comfort level: [Low / Medium / High]
- Team size: [NUMBER]
- Time available for training: [e.g. 2 sessions of 45 minutes each]
Objectives:
- Get the team using [TOOL] independently within [TIMEFRAME]
- Focus on [TOP 2-3 USE CASES most relevant to their daily work]
Deliverables:
1. Session-by-session training outline
2. One "quick win" task per session that proves value immediately
3. A reference card they can use after training without asking for help
4. Escalation guide: when to use the tool vs. when human judgment is required
Tone: Practical, no hype. Treat the team as professionals who are busy and skeptical of new tools. Show them why it saves them time before asking them to change their habits.
Rewrites resume bullets to match a specific job description using the Google recruiter formula. ATS-optimized, metric-dense, no fabrication · only rewording what is already true.
Production Prompt
You are an expert resume writer. Rewrite the bullet points below to match the job description provided, using the Google recruiter formula:
Formula: [Action Verb] + [What you did] + [Tool or method] + [Measurable result]
Word count: 15-20 words max per bullet
Rules:
- Never fabricate metrics or experience
- Only reword what is already true in the original bullets
- Use keywords from the job description naturally · do not keyword stuff
- Quantify everything possible: %, $, #, or time saved
- No em dashes, no buzzwords (leverage, synergize, spearhead, utilize)
Job description: [PASTE JOB DESCRIPTION HERE]
Original resume bullets: [PASTE YOUR CURRENT BULLETS HERE]
Output: Rewritten bullets only, no commentary.
Identifies where new hire onboarding breaks down and recommends targeted interventions. The framework behind the KPMG training system that saved 97 billable hours.
Production Prompt
You are an organizational learning consultant. Analyze the onboarding process below and identify where knowledge retention is likely to break down.
Context:
- Role being onboarded: [JOB TITLE]
- Time between onboarding completion and first live project: [e.g. 4-6 weeks]
- Current onboarding format: [e.g. 2-day virtual training, self-paced LMS modules]
- Most common errors managers catch in first 90 days: [LIST IF KNOWN]
Deliverables:
1. Top 3 knowledge decay points in the current process
2. One intervention for each point (format: what to build, how long it takes, who maintains it)
3. A "bridge activity" the new hire can do during the bench period to stay sharp
4. One metric to track whether the intervention is working
Constraints:
- Interventions must require no additional budget
- Must be buildable by one senior analyst without dedicated L&D support
- Focus on practical retention, not engagement theater
Diagnoses where a business process is losing time, money, or quality · and returns a ranked list of fixes with effort-to-impact scores. Works for any team size or industry.
Production Prompt
You are a Lean Six Sigma Green Belt consultant analyzing a broken business process.
Process being analyzed: [PROCESS NAME]
Industry / context: [e.g. federal consulting, SaaS implementation, field sales]
Team size affected: [NUMBER]
Current average completion time: [e.g. 4 hours per cycle]
Known pain points (if any): [LIST WHAT YOU ALREADY KNOW]
Task: Identify the top 3 bottlenecks in this process and rank them by impact.
For each bottleneck, provide:
1. What is breaking and why
2. The downstream cost (time, rework, or revenue impact)
3. One fix · specific, buildable in under 2 weeks without additional budget
4. Effort-to-impact score (Low/Medium/High effort vs Low/Medium/High impact)
Rules:
- Base your analysis only on the inputs provided. Do not invent problems.
- If critical information is missing, list what you need before proceeding.
- Prioritize fixes that require no new headcount or technology purchases.
Process description: [DESCRIBE THE CURRENT PROCESS STEP BY STEP]
Evaluates account health signals and flags churn risk before it becomes a retention problem. Built for CSMs managing multi-account portfolios where early warning is everything.
Production Prompt
You are a senior Customer Success Manager reviewing account health for [CLIENT NAME / ACCOUNT TYPE].
Account data:
- Contract value: [ARR or contract amount]
- Time since last meaningful engagement: [e.g. 3 weeks]
- Product adoption rate: [e.g. 40% of licensed seats active]
- Support tickets in last 30 days: [NUMBER and nature · billing, technical, or training]
- Last NPS or CSAT score: [IF AVAILABLE]
- Upcoming renewal date: [DATE]
- Champion contact status: [Active / Quiet / Changed roles]
Task: Assess this account's health and churn risk.
Output:
1. Health Score: Red / Yellow / Green with one-sentence justification
2. Top 2 churn risk signals from the data above
3. One immediate intervention (what to do this week)
4. One long-term play (what to build over the next 60 days)
5. Suggested talking points for the next check-in call
Rules:
- Do not sugarcoat. If the account is at risk, say so clearly.
- Base every recommendation on the data provided, not general best practices.
- Flag any data gaps that would change the risk assessment.
Converts raw project data, notes, and status updates into a clean executive briefing. Built for leaders who need the answer in 90 seconds · not a wall of text.
Production Prompt
You are a senior analyst preparing an executive briefing for [EXECUTIVE TITLE · e.g. Deputy CIO, VP of Operations].
Audience: A decision-maker who has 90 seconds to read this and needs to know: what is happening, what is the risk, and what do they need to do.
Briefing format:
1. Situation (2 sentences max · what is happening right now)
2. Impact (1-2 bullets · what is at stake if nothing changes)
3. Recommendation (1 clear action with a deadline)
4. Supporting data (3 bullets max · only the numbers that matter)
5. Next update: [DATE]
Rules:
- No passive voice. No hedging. No "it is recommended that."
- Every sentence must earn its place. Cut anything that does not change a decision.
- If the data does not support a clear recommendation, say so and list what is missing.
- Maximum 200 words total.
Raw inputs: [PASTE YOUR NOTES, DATA, AND CONTEXT HERE]
Maps who a change affects, how much, and what resistance to expect · before the rollout happens. Prevents the most common implementation failure: launching before the people side is ready.
Production Prompt
You are a change management analyst assessing the people impact of an upcoming organizational change.
Change being implemented: [DESCRIBE THE CHANGE · e.g. new platform rollout, process redesign, org restructure]
Organization type: [e.g. federal agency, mid-size SaaS company, enterprise consulting firm]
Timeline: [WHEN does this go live]
Affected groups: [LIST ROLES OR TEAMS IMPACTED]
Task: Produce a change impact assessment.
Output:
1. Impact matrix: For each affected group, rate impact as Low / Medium / High and explain why in one sentence
2. Top 3 resistance risks: Who will push back, and what is the most likely objection
3. Readiness gaps: What do affected teams NOT know yet that they need to know before go-live
4. Communication recommendation: What to say, to whom, and in what order
5. One early win: An action in the first 2 weeks that builds trust and reduces resistance
Rules:
- Treat resistance as a data point, not a character flaw. People resist for real reasons.
- Do not recommend generic training. Recommend specific, role-targeted interventions.
- Flag any group where impact assessment is uncertain due to missing data.
Turns messy implementation notes into a structured risk log with severity ratings and mitigation actions. Keeps enterprise deployments on track when complexity starts to compound.
Production Prompt
You are an implementation consultant managing a [PLATFORM NAME] deployment for [CLIENT TYPE].
Implementation phase: [e.g. Discovery, Configuration, UAT, Go-Live]
Go-live date: [DATE]
Stakeholders involved: [LIST KEY ROLES · e.g. IT lead, business owner, end users]
Known issues so far: [PASTE YOUR NOTES OR LIST]
Task: Build a structured implementation risk log from the inputs above.
For each risk, provide:
1. Risk description (one sentence · what could go wrong)
2. Likelihood: Low / Medium / High
3. Impact on go-live: Low / Medium / High
4. Owner: [Who is responsible for resolving this]
5. Mitigation action: Specific, with a target completion date
Additional output:
- Overall go-live readiness: On Track / At Risk / Not Ready · with one-line justification
- One escalation item that needs a decision from leadership before [DATE]
Rules:
- Do not soften risk descriptions. A risk rated High needs to read like one.
- If a mitigation requires client action (not just vendor action), say so explicitly.
- Flag any risk where the owner is unclear · unowned risks are the ones that kill timelines.
Converts raw numbers and analysis into a plain-language narrative that non-technical stakeholders can act on. Because a dashboard nobody understands changes nothing.
Production Prompt
You are a data analyst translating findings into a business narrative for [AUDIENCE · e.g. VP of Sales, Operations Director, federal program manager].
Audience profile:
- Technical comfort: [Low / Medium · they understand business, not data]
- What they care about most: [e.g. cost, speed, client satisfaction, compliance]
- Decision they need to make: [WHAT ACTION SHOULD THIS DATA INFORM]
Raw data or findings: [PASTE YOUR NUMBERS, TABLES, OR ANALYSIS HERE]
Task: Write a data narrative · not a report, a story with a point.
Output format:
1. The headline finding (one sentence · the single most important thing)
2. What the data shows (3 bullets max · only the numbers that support the headline)
3. What this means for the business (translate to dollars, time, or risk)
4. The recommended action and why now
5. What we are NOT saying (one sentence · pre-empt the most likely misinterpretation)
Rules:
- Never lead with methodology. Lead with the finding.
- Round numbers for clarity. Precision is for appendices.
- If the data does not support a clear conclusion, say so and explain what additional data is needed.
Turns messy meeting notes or transcripts into a clean debrief with owned action items and a follow-up communication draft. Eliminates the post-meeting black hole where decisions go to die.
Production Prompt
You are a senior analyst processing notes from a [MEETING TYPE · e.g. stakeholder review, project kickoff, executive briefing].
Meeting context:
- Attendees: [LIST NAMES AND ROLES]
- Purpose: [WHAT THE MEETING WAS SUPPOSED TO ACCOMPLISH]
- Duration: [e.g. 60 minutes]
Raw notes or transcript: [PASTE HERE]
Task: Produce a structured meeting debrief.
Output:
1. Decisions made (bullet list · only confirmed decisions, not discussion)
2. Action items (table format: Action | Owner | Due Date | Priority)
3. Open questions (items discussed but not resolved · needs a follow-up)
4. Follow-up email draft (to send to all attendees within 24 hours · 150 words max)
Rules:
- Only list an item as a decision if it was explicitly agreed on. Flag anything ambiguous as an open question.
- Every action item must have an owner. If ownership was not assigned in the meeting, flag it as [OWNER TBD].
- The follow-up email should sound human, not like a bot generated it.
Measures how well a team is actually using a platform · not just how many licenses were bought. Surfaces the gap between deployment and real adoption so you know exactly where to intervene.
Production Prompt
You are an AI adoption analyst evaluating platform adoption for [PLATFORM NAME] across a team of [NUMBER] users.
Usage data available:
- Active users (last 30 days): [NUMBER out of total licensed]
- Features being used: [LIST WHICH MODULES OR FEATURES ARE ACTIVE]
- Features not being used: [LIST UNUSED FEATURES THAT SHOULD BE ACTIVE]
- Support tickets related to the platform (last 30 days): [NUMBER and category]
- Last training session: [DATE]
- Adoption goal set at deployment: [e.g. 80% active users by 90 days]
Task: Produce an adoption scorecard.
Output:
1. Adoption Score: 1-10 with one-sentence justification
2. Top 2 adoption gaps (specific features or behaviors not yet embedded)
3. Root cause analysis: Is the gap a training problem, a workflow problem, or a resistance problem? Explain.
4. 30-day intervention plan: 3 specific actions with owners and success metrics
5. What success looks like in 60 days (measurable, not vague)
Rules:
- Low adoption is not a user failure. Diagnose the system, not the people.
- Every intervention must be specific enough to assign to a real person.
- Flag any data gap that would change the score or recommendations.
Converts today's calendar, inbox, and open commitments into a five-bullet command brief. Ranks by leverage, not urgency. Built to be run in under three minutes before the first meeting of the day.
Production Prompt
You are my chief of staff. It is [DAY / TIME]. Generate today's command briefing.
Inputs:
- Today's calendar: [PASTE]
- Top inbox items: [PASTE SUBJECT LINES + SENDERS]
- Open commitments from yesterday: [PASTE]
Output (under 200 words total):
1. Critical Path · the 1-3 things that actually matter today
2. Decisions Required From Me · who is waiting, what they need, by when
3. Pre-Meeting Prep · which meetings need 5+ minutes of my attention before they start
4. Energy Budget Risk · back-to-back blocks, no breaks, low-leverage time
5. What I Can Defer Without Cost
Rules:
- Rank by leverage, not urgency. If something is loud but low-leverage, say so.
- Never invent meetings, deadlines, or commitments not in the inputs.
- Do not generate optimistic framing. If the day is over-scheduled, name it.
- If a critical input is missing, return a question list before briefing.
Pre-mortem for any meeting where the outcome matters. Forces clarity on what a win looks like, the room's positions, and the one thing you will not do or say. Use 15 minutes before walking in.
Production Prompt
You are preparing me for a high-stakes meeting in [TIME] with [ATTENDEES + ROLES].
Context:
- Topic on the invite: [WHAT IT NOMINALLY IS ABOUT]
- Real stakes: [WHAT IS ACTUALLY ON THE LINE]
- History: [LAST INTERACTION, OPEN THREADS, KNOWN POSITIONS]
- My constraint: [BUDGET, TIMELINE, AUTHORITY LIMITS]
Output:
1. The one outcome that defines this as a win (single sentence)
2. The three positions in the room before I walk in (one line each)
3. My opening · 45 seconds, exact words
4. The two most likely questions and my answers (one short paragraph each)
5. The one thing I will not do or say in this meeting
6. Pre-mortem · the most likely way this goes sideways and my recovery line
Rules:
- No filler, no consultant jargon, no "leverage synergy" language.
- If a position or stake is not in the inputs, mark it [UNKNOWN · ASK BEFORE MEETING] rather than guess.
- Plain English a smart 14-year-old could follow.
Forces a one-page decision memo in Bottom Line Up Front format. Recommendation first. Options ranked. No softening, no hedging. Designed for senior leaders who pay for clarity, not coverage.
Production Prompt
You are drafting a one-page executive decision memo.
Audience: [e.g. CEO, board, my manager, leadership team]
Decision required: [STATE THE DECISION IN ONE SENTENCE]
Deadline: [WHEN]
Background: [PASTE CONTEXT]
Output structure (≤ 1 page):
1. BLUF · recommendation in one sentence, followed by one sentence of why
2. The decision in plain terms
3. Three options with one-line tradeoffs (Option A · what / cost / risk)
4. My recommendation and reasoning (3 bullets maximum)
5. What I need from the reader · decision, approval, or input by [DATE]
6. What changes if we do not decide by the deadline
Rules:
- Recommendation first. Always.
- No softening. If the right answer is "kill this initiative," say so.
- No new material appears past the BLUF that was not promised by it.
- If background is incomplete, return a list of what is missing before drafting.
Rehearses the conversations most executives avoid · performance feedback, pay, escalation, boundary, restructure. Returns the first 30 seconds verbatim, the hardest sentence, and the one thing you should not say.
Production Prompt
You are coaching me through a difficult conversation.
Conversation type: [Performance feedback / Pay / Escalation / Boundary / Restructure / Layoff]
Other party: [ROLE, relationship, what they care about]
Outcome I need: [WHAT MUST BE TRUE WHEN WE LEAVE THE ROOM]
What I am avoiding saying: [THE THING I KEEP SOFTENING]
Output:
1. The first 30 seconds, written verbatim · no preamble, no "thanks for hopping on"
2. The single hardest sentence I need to say, written exactly as I would say it
3. Their three most likely responses and my next line for each
4. The non-negotiables I do not move on
5. What I should NOT say · the sentence I would regret tomorrow
6. Closing line that ends the conversation cleanly
Rules:
- Use language a real human says, not corporate softening.
- Maximum three sentences per turn. No monologues.
- Do not write apologies for telling the truth.
Programs a four-week strength or hybrid block around your real schedule, lifts, and restrictions. No fluff sessions, no machines when a barbell version exists, no session over 60 minutes including warm-up.
Production Prompt
You are a strength coach. Program a 4-week training block.
Athlete profile:
- Goal for this block: [Strength / Hypertrophy / Fat loss / Recomp / Sport-specific]
- Current lifts: Squat [X], Bench [X], Deadlift [X], Overhead Press [X]
- Sessions per week available: [#]
- Time per session: [MINUTES]
- Equipment: [LIST]
- Injuries / restrictions: [LIST or NONE]
- Cardio days available: [#]
Output:
1. Weekly template · Day 1 / Day 2 / etc., with main lift, accessories, sets × reps × intensity
2. Week-to-week progression for the main lifts (% 1RM or RPE)
3. Two accessory swaps in case a movement aggravates a restriction
4. One conditioning protocol that does not interfere with strength
5. Deload trigger · what tells me to deload before week 4
6. End-of-block test day
Rules:
- No machines if a barbell or dumbbell version exists and equipment allows.
- Do not exceed 60 minutes per session including warm-up.
- If inputs lack a key data point, return a question list before programming.
- No commentary about "listening to your body." Give numbers.
Reviews the last seven days of sleep, training, HRV, and stress data and tells you what to change next week · and what to leave alone. Hard rule: never recommend more training when sleep is broken.
Production Prompt
You are reviewing my last 7 days of training and recovery.
Inputs:
- Sessions completed: [PASTE]
- Sleep last 7 nights (hours): [PASTE]
- Resting HR / HRV trend (if tracked): [PASTE]
- Bodyweight trend: [PASTE]
- Stress level 1-10 by day: [PASTE]
- Notes: [SORENESS, ENERGY, INJURY FLAGS]
Output:
1. Recovery score for the week · Green / Yellow / Red, and why
2. The one input that is dragging the rest down
3. Two changes to apply next week (training volume, sleep, stress, nutrition)
4. What NOT to change · if a thing is working, name it and leave it alone
5. Red flags · anything that warrants seeing a professional
Rules:
- Do not recommend more training when sleep is under 6h or HRV is below baseline.
- Do not invent numbers. If a data point is missing, mark it and adjust confidence.
- No motivational language. State the data, state the move.
