Prompt Library

A blunt read on whether a role is worth applying for, before any resume work starts.

Check whether vision and stakeholder-navigation answers actually landed with the panel.

A specific breakdown of which answers actually demonstrated seniority-level impact.

Check specifically how the career-change story landed, not just general performance.

An honest breakdown of what went well and what didn't, right after an interview.

Identify whether searches keep stalling at the same stage — competence, board fit, or comp.

Even senior roles get filtered by automated screening — check before assuming a network intro is enough.

A direct read on whether to engage with a search before investing real time in it.

Find where applications consistently break down across recent searches.

Compare a resume against a posting the way an applicant-tracking system would.

A blunt read on real fit and interview risk before spending an evening on an application.

Find whether the pivot itself, or something else, is where applications keep breaking down.

Translate resume language into the target field's own vocabulary where it will actually score.

An honest read on whether a career-change application is realistic, before writing anything.

Find where applications consistently break down, instead of reading each rejection alone.

Compare a resume against a posting the way an applicant-tracking system would.

A tight, third-person bio built on scope, highlights, and credentials.

Tighten a public announcement to read as warm and forward-looking.

Clarifying questions that reveal real equity value and risk.

A complete, point-by-point response covering every part of the offer.

Tailored talking points for each stakeholder type on the panel.

A point-of-view-driven answer grounded in a concrete past example.

A specific, time-respectful ask to a senior contact.

A warm reply that keeps the relationship open regardless of current interest.

A scope-forward headline plus outcome-first achievement bullets.

A respectful request that gives the contact an easy out.

A discreet outreach message for someone currently employed and searching.

Reposition an existing 'About' section around current direction.

Ordered talking points with a fallback response for each likely objection.

A warm, data-anchored counter to a job offer.

A realistic practice question plus a structured way to reason through it.

A STAR-format answer built around ownership of outcomes.

A tight, achievement-focused cover letter tied to the posting's priorities.

Rewrite bullets to lead with outcome and quantified impact.

Just enough industry context to sound credible in a first interview.

Acknowledge a gap directly, then pivot to the closest relevant evidence.

A confident, forward-looking answer to the question every career changer gets.

Questions that reveal what breaking into a new field actually takes.

An honest, specific outreach message for breaking into unfamiliar territory.

Rewrite existing bullets using the target field's language, without inventing facts.

Addresses the pivot head-on and connects it to the new role's requirements.

A short summary that frames a career change as a strength, not a risk.

Map current experience onto the target industry's own vocabulary.

A specific, prompt thank-you email referencing the actual conversation.

A realistic 4-week plan plus a spreadsheet tracker layout.

A short, low-pressure request for a 15-20 minute informational call.

Searchable, specific headline alternatives to the default job title.

A first-person 'About' section built from education, internships, and skills.

Likely questions plus one full STAR-format practice answer.

A structured, role-focused opening answer for entry-level interviews.

Turn limited work experience into believable, relevant resume bullets.

A tailored, concise cover letter connecting background to the posting's requirements.

Give a preliminary enforceability risk read on a non-compete clause under a named jurisdiction.

Flag copyleft licenses in a dependency list and how distribution model changes exposure.

Turn case notes into a status-led internal memo separating established from disputed facts.

Structure a research brief around the sub-questions it needs to answer, no invented citations.

Identify and rank the top fact-grounded leverage points for an early settlement.

Draft narrow, leading cross-examination questions that build toward specific points.

Identify change-of-control, anti-assignment, and acquisition-triggered termination provisions.

Build a specific, dealbreaker-flagged compliance questionnaire for a new vendor.

Announce a policy change with the effective date and required action stated clearly up front.

Turn a policy into training talking points with a worked example scenario.

Identify the specific gap between current practice and a new regulatory requirement.

Flag potential sanctions risk points in a supply chain routing for further verification.

Flag which jurisdictions and legal bases are likely implicated by a new data practice.

Draft a breach notification template flagged for jurisdiction-specific confirmation.

Respond to negotiation pushback on a specific clause, offering only real flexibility.

Rewrite dense policy text for general staff while preserving every actual obligation.

Draft a policy section with clear obligations and consequences, not vague aspirational language.

Translate a contract into the operational obligations a non-legal team actually needs.

Rank open deal points by priority with a target and fallback position for each.

Summarize exit rights, notice/cure requirements, and surviving obligations.

Break down who bears what risk under an indemnification clause and flag asymmetries.

Draft specific replacement language for a flagged clause, with negotiation-difficulty notes.

Draft a starting NDA with standard sections and flagged inputs still needed.

Draft a section-by-section vendor agreement outline covering named risk areas explicitly.

Review an incoming agreement and flag risky or non-standard clauses in plain business terms.

Draft a board resolution with standard structure and flagged placeholders for missing specifics.

Draft alternative independent claim variations that meaningfully differ in scope.

Review your own notes for missing foundational concepts before an exam, not just typos.

Build a timed session plan with at least one active element, not lecture-only.

Draft a specific, example-grounded recommendation letter with placeholders for details you supply.

Write ordered discussion questions that avoid single-right-answer recitation.

Write feedback that ties every point back to a specific rubric criterion.

Generate a grading rubric with concrete, distinguishing descriptions per performance tier.

Write assessable learning objectives using measurable action verbs, not vague ones.

Design a week-by-week syllabus that builds logically toward stated learning goals.

Draft an accurate, brief recap of an office hours conversation and its next steps.

Get a direct craft-level review of a draft paragraph for passive voice, clarity, and flow.

Shortlist journals by fit with your topic and stated priorities, flagging tensions between them.

Build a full essay outline with thesis, evidence-backed body points, and a counter-argument.

Draft a respectful, point-by-point response to every reviewer comment.

Draft a word-limited abstract where every claim traces back to the given content.

Flag genuine numerical or logical inconsistencies in reported findings before submission.

Get a peer-reviewer-style critique flagging real, fixable methodological weaknesses.

Design a multi-database search strategy with controlled vocabulary, not just keywords.

Interpret statistics in plain language, separating statistical from practical significance.

Get a justified method recommendation with assumptions, checks, and a fallback.

Turn your own paper summaries into a coherent, gap-stating literature review section.

Explain a hard concept using a real-world analogy that actually maps onto the mechanism.

Turn a bureaucratic policy document into a clear, actionable faculty email.

Prioritize what a new engineer needs day 1 vs. what they’ll pick up naturally.

Turn an informal workflow description into a proper, followable SOP.

Audit an existing SOP for ambiguity or missing steps and propose specific fixes.

Build a time-budgeted agenda ordered by priority and marked for decision vs. info items.

Turn raw meeting notes into decisions, owned action items, and open questions.

Request a status update from a vendor with a specific, professional ask.

Escalate a vendor problem internally, leading with business impact.

Write a blameless, factual incident report with a clear timeline.

Propose preventive measures that trace directly to the incident’s root cause, ranked by effort vs. impact.

Turn audit findings across several processes into a single prioritized improvement list.

Turn raw progress notes into a status-led update with a clear decision-needed flag.

Condense a detailed status into exactly 3 sentences that never hide a risk.

State a project risk plainly with mitigation trade-offs and one clear recommendation.

Escalate a blocker with a specific ask and deadline stated up front.

Turn stakeholder conversation notes into scoped must-haves and nice-to-haves.

Document a scope change with impact and required approval, even if impact is unconfirmed.

Structure retro notes into what went well, what to fix, and top takeaways.

Turn a retrospective into forward-looking, actionable guidance for future projects.

Categorize mixed project notes strictly into Risks, Assumptions, Issues, or Dependencies.

Draft a scheduling email that offers specific time options instead of an open-ended ask.

Notify attendees of a reschedule clearly, without over-apologizing.

Turn raw booking confirmations into a chronological itinerary with flagged risks.

Turn trip details into an approval-ready travel request with an honest cost estimate.

Clean up and structure a raw report for distribution without altering its substance.

Categorize and total a raw expense list, flagging anything that does not fit a category.

Draft a message matching a described executive tone and covering every key point given.

Draft a brief, specific acknowledgment note tied to the actual thing being thanked for.

Announce a logistical change with practical impact and dates stated up front.

Write a 2-3 sentence headline for a release, led by the single most important change.

Generate a PRD outline with problem statement, success metrics, and open questions flagged.

Write Given-When-Then user stories including at least one edge case.

Build distinct, research-grounded personas rather than variations of the same person.

Communicate a roadmap change and address anticipated pushback directly.

Categorize features into Must/Should/Could/Won’t have with a rationale per item.

Identify defensible product gaps against a named competitor, ranked by user impact.

Classify and prioritize incoming tickets, flagging duplicates and under-specified ones.

Ask only the questions that would actually help diagnosis, plus one thing to try meanwhile.

Order fixes from simplest to most involved, written for the user’s stated technical level.

Rank likely causes of a recurring technical error and give a confirm step for each.

Communicate an ongoing outage, committing to a next-update time instead of a guessed ETA.

Confirm resolution clearly and only mention prevention if something concrete is planned.

Generalize a resolved ticket into a self-service KB article with an escalation path.

Flag specific outdated statements and gaps in an existing KB article, with fixes.

Build an IT setup checklist ordered by timing, with approvals flagged separately.

Turn an informal, rambling explanation into a structured, precise internal doc.

Draft a compliance-framework-aligned policy template, flagging where current practice likely falls short.

Document an endpoint fully, with a realistic example request/response, not placeholders.

Turn informal technical notes into a numbered guide with prerequisites and checkpoints.

Explain system architecture component-by-component, including the why behind decisions.

Write a blameless postmortem with a real timestamped timeline and separated fix/prevention.

Extract action items that trace to specifics in the postmortem, prioritized against team capacity.

Recommend architecture changes justified by a specific scale target, with trade-offs stated.

Translate a raw changelog into grouped, benefit-focused release notes.

Group survey/interview feedback into ranked themes with representative quotes.

Break a budget variance down into ranked, quantified contributing causes.

Check forecast assumptions against historical actuals and flag internal inconsistencies.

Model the combined cash flow impact of several assumptions at once.

Spot genuine trends and one-off anomalies across multi-year income statement data.

Turn call notes or a transcript into specific, balanced coaching feedback with one thing to try next.

Turn a list of common objections into one clear recommended response each, not a menu.

Build talk-track USPs against a named competitor, grounded in real strengths and weaknesses.

Find the highest-leverage funnel stage to fix, not just the lowest-looking number.

Draft a short, conversion-focused cold email that leads with the prospect’s problem.

Summarize a standup for people who missed it, led by the most consequential update.

Propose tactics for a specific funnel stage’s drop-off, separating quick fixes from process change.

Flag stalled or low-quality deals in the pipeline and suggest the action each one needs.

Turn pipeline data into a forecast with stated confidence and the deals it depends on.

Equip an internal champion with a one-pager to sell the deal internally.

Summarize a deal’s history for a receiving team so they can act without reading everything.

Prepare a grounded response to pushback on a specific contract term, with a fallback.

Provide multiple distinct, value-grounded frameworks for handling "too expensive."

Follow up on silence without guilt-tripping, with an easy yes/no response option.

Follow up after a demo referencing specifics and closing any open question.

Turn metrics and qualitative notes into a performance summary with specific next steps.

Document a reconciliation discrepancy with what has been ruled out and the next concrete step.

Build a proposal that ties every recommendation back to a pain point raised in the demo.

Explain a budget decision to an affected department head directly and honestly.

Analyze liquidity and leverage ratios from balance sheet data.

Turn a list of finance terms into a plain-language glossary with examples.

Write an unambiguous, reproducible definition for a financial metric.

Turn raw results into a board update that leads with what matters.

Turn a variance analysis into a short, non-defensive message for the department head.

Turn a completed reconciliation into a short summary a manager can review quickly.

Draft a payment reminder matched to the escalation stage.

Query a vendor about an invoice discrepancy professionally and specifically.

Turn dense legal and financial-commitment footnotes into a bulleted, traceable summary.

Extract every financial obligation and deadline from a contract, flagging ambiguity.

Turn an informal close process into an ordered checklist with dependency and bottleneck notes.

Map raw call notes to specific CRM fields and flag missing required data.

Turn raw close progress notes into a status update that flags real risk to the target date.

Categorize transactions against a chart of accounts and flag genuinely ambiguous ones.

Rewrite expense policy so staff understand limits and rules without finance jargon.

Turn an OPEX breakdown and savings target into a ranked, risk-flagged action plan.

Flag vendor spend candidates for renegotiation or cancellation based on utilization and renewal timing.

Score default risk from financial ratios and flag what data would sharpen the read.

Translate a regulatory update into a concrete gap-and-action summary against current practice.

Summarize a contract’s financial terms and risk for a non-legal decision-maker.

Compare current vs. proposed renewal terms and give a grounded recommendation.

Turn a financial decision and its reasoning into a short, sign-off-ready memo.

Write a sub-300-character LinkedIn connection request that earns the connection before pitching.

Build a varied-angle outbound cadence that ends with a genuine breakup message.

Build a short, context-aware follow-up sequence for a warm inbound lead.

Write ordered qualifying questions that would disqualify a bad-fit prospect, not just confirm interest.

Turn raw research notes into a one-screen pre-call brief with usable talking points.

Respond to early rejection without arguing, keeping the door open with one low-pressure alternative.

Respond to a redirect or info request while still moving the deal forward.

Score and tier a new account list against the ideal customer profile.

Draft a cover message for a formal quote that highlights what matters most to this buyer.

Announce a schedule change with the effective date up front and a clear ask.

Generalize a real playbook from several similar resolved tickets.

Turn tribal knowledge into a step-by-step SOP a new agent can actually follow.

Prepare talking points for a calibration session that resolve genuine rubric ambiguity.

Score an agent response criterion-by-criterion with quoted justification.

Turn a customer report into an engineering-ready bug escalation, facts only.

Condense a long thread into a summary the receiving team can act on immediately.

Turn raw observations into a structured health note that separates signal from opinion.

Turn a QBR deck into talking points, with a prepared response to the likely pushback.

Build ready-to-use Boolean search strings for LinkedIn, Google X-ray, or GitHub.

Build an outline that supports a specific angle, not a generic topic overview.

Turn period-over-period metrics into an outcome-led QBR narrative.

Build a save plan that responds directly to the stated reason for risk.

Reach out to an at-risk account without naming the internal risk signal.

Open an upsell conversation as a solution to a real signal, not a sales pitch.

Lead with delivered value, not the admin ask, when approaching a renewal.

Turn a raw list of items into a newsletter with one clear lead story and CTA.

Write interview questions that probe for the specific failure pattern of past hires.

Prepare a neutral, forward-looking set of talking points for mediating a team conflict.

Turn messy notes into a short, well-organized team update.

Turn loose goal ideas into measurable goals that ladder up to real priorities.

Turn scattered notes collected over a period into a proper written review.

Prepare a direct, specific opening for a hard 1:1 conversation.

Turn what has been going on into a focused, actionable 1:1 agenda.

Build a question set tailored to a specific departure, not a generic template.

Draft a short, unbiased engagement survey on a specific focus area.

Draft a clear internal announcement that addresses the obvious concern head-on.

Draft a direct, measurable PIP grounded only in the facts given.

Design a full review template with anchored rating scales for a role/level.

Generate a grounded FAQ from a policy so employees stop pinging HR for the same answers.

Build a concrete, milestone-based ramp plan for a new hire.

Build a competency-based scorecard with anchored 1-5 ratings.

Build a consistent, fast-to-apply screening rubric for a role.

Draft a personalized first-touch outreach message that does not sound like a template.

Write a rejection message that is warm and clear without inviting a debate.

Turn raw interviewer notes into a calibration summary that surfaces disagreement instead of hiding it.

Prepare targeted phone-screen questions from a role and a specific CV.

Turn raw, unstructured candidate notes into a clean, comparable longlist.

Turn offer details into a friendly summary email ahead of the formal letter.

Translate dense policy text into something an employee can understand in one read.

Draft a warm, practical welcome message to send before day one.

Build a multi-email sequence that builds toward a goal instead of repeating itself.

Generate a batch of shoot/write-ready post ideas across defined pillars.

Draft replies matched to each comment’s tone, with support-routing flagged separately.

Write hero copy where the headline states the benefit, not a clever tagline.

Draft a short holding statement that states only what is confirmed.

Answer what was actually asked, with a specific next step if you need to route elsewhere.

Pull genuinely standalone short-form posts out of a long-form source.

Adapt a post to a new platform’s norms while preserving the core message exactly.

Build a week-by-week posting calendar with pillars evenly distributed.

Write multi-slide copy where each slide advances one idea and slide one hooks alone.

Write a caption with a first-line hook and platform-correct conventions.

Generate one-sentence thumbnail concepts tagged by the emotional hook they use.

Turn a visual reference into concrete, reusable language for image-gen prompting.

Derive documented voice traits from actual on-brand copy, not generic adjectives.

Generate one clearly-labeled ad variant per angle so a test isolates the real variable.

Write ad copy and a matching image concept designed together, not separately.

Write two hero variants that isolate a real hypothesis, not just different wording.

Write an image-generation prompt for a social post, with text-overlay handled correctly.

Draft a kickoff message grounded in the goals the customer actually stated.

Write an image-generation prompt with explicit lighting, composition, and style.

Adapt one long piece into multiple standalone derivative formats.

Write click-worthy metadata that respects length limits and includes the keyword naturally.

Write benefit-led landing copy that addresses real objections instead of ignoring them.

Draft a positioning statement where every claim maps to a real proof point.

Turn a loose campaign idea into a proper, measurable brief.

Turn an approved outline into a full draft, flagging any claim that needs a source.

Build a quantified case for opening a new role.

Write a blameless, factual postmortem from raw incident notes.

Summarize a period for the whole team, not just the next shift.

Build a data-grounded 30-day check-in message and call agenda.

Turn raw notes into an urgency-ordered handoff for the next shift.

Draft an internal note requesting an exception, including the precedent risk.

Explain a refund or policy decision clearly, without sounding condescending.

Flag outdated, redundant, or unclear macros and recommend fixes.

Convert a one-off reply into a variable-driven macro the whole team can reuse.

Draft an apology that leads with ownership, not a buried fix.

Open a reply to an angry customer without generic "I understand your frustration" language.

Adjust an existing draft to the right tone without changing what it says.

Draft a clear, correctly-toned reply to a support ticket.

Draft a short, honest team charter that addresses actual friction points.

A general coach for planning and improving your own social content.

A full strategy pass — positioning, pillars, cadence, and a 30-day plan.

Translate academic text without losing terminology, register, or meaning.

Pick a defensible statistical method for your thesis before you run the wrong test.

Work through a draft one problem at a time instead of getting a rewritten black box back.

Turn a plain block of text into open questions without needing a full source document.

Generate open questions that test understanding of a specific source document.

Turn any chapter or lecture into exam-grade multiple-choice questions with plausible distractors.

A general-purpose feedback prompt for when you have no rubric and just want an honest read.

Give one example question and get a matched set in the same style and difficulty.

One-pass improvement when you just need a cleaner version fast.

Get a summary shaped for how you will actually use it, not a generic abstract.

Turn scrappy margin notes into elaborate, usable written feedback.

Grade your own open-question answers against a defined solution space before the real exam does.

Use AI as a tutor that tests you, instead of one that just explains at you.

Build a proper search strategy instead of typing your topic into Google Scholar and hoping.