Prompt library

Prompts you can copy and use today

Every prompt here follows the FRAME method. Bracketed items are yours to edit: swap in your audience, your word count, your document.

The FRAME method

F
Frame the job.
Give the AI a role and a clear definition of done. Not "help with this policy," but "You are an HR communications specialist. Rewrite this policy for frontline employees at a ninth-grade reading level."
R
Real context.
Add the constraints the model cannot know: your audience, your plan year, your comp philosophy, what is off-limits. This is the step people skip, and it is the one that matters most.
A
Add your source.
Paste the actual messy input: the real job description, the real policy, the real de-identified data. Grounding beats guessing every time.
M
Model the output.
Say exactly what you want back: the format, the length, the tone, and one example of "good." Showing one example beats describing ten rules.
E
Evaluate and iterate.
Treat the first answer as a draft, never a deliverable. Refine it in plain language, then audit it against the Human Stewardship Model before it goes anywhere near an employee.

Communications

Manager talking points for a change

When to use: Rolling out a policy, comp, or benefits change and managers need to speak to it.

You are an HR communications partner. From the update below, write manager talking points for a [15-minute] team conversation: a two-sentence summary, the three things employees will care about most, three likely questions with plain answers, and one line on where to send people for more help. Keep it under [250] words.

[paste the update]

Benefits

Turn a policy into a plain-language FAQ

When to use: Any dense policy or plan document employees actually have to read.

You are an HR benefits writer. Turn the policy below into a plain-language FAQ for [hourly employees] at a [sixth]-grade reading level. Use a question-and-answer format, [eight] questions maximum, keep every rule intact, and flag anywhere the language is ambiguous instead of guessing.

[paste the policy]

Interrogate a document before employees do

When to use: Pressure-test a plan document or handbook for gaps.

You are a skeptical employee reading the document below for the first time. List the ten questions you would ask that the document does not clearly answer. For each one, quote the closest relevant line, or say "not addressed."

[paste the document]

Compensation

Clean up and sanity-check a job description

When to use: A messy JD, or checking a role against your leveling.

You are a compensation analyst. Rewrite the job description below into a clean, consistent format with sections for summary, key responsibilities, and required qualifications. Remove duplication and vague filler. Then flag any responsibilities that read above or below the stated level, and explain why.

[paste the JD]

Talent

Draft consistent, role-specific interview questions

When to use: Bringing consistency and fairness to interviews.

You are a talent partner. From the role summary below, generate [eight] structured interview questions that assess the core competencies for this role. For each, add what a strong answer includes. Keep every question job-related and avoid anything that could touch protected characteristics. These support the interviewer's judgment; they do not replace it.

[paste the role summary]

Editing

Score and improve a draft against a rubric

When to use: Offer letters, comms, anything with clear quality criteria.

Score the draft below against these five criteria [list them], each out of five with a one-line reason. Then rewrite the draft to raise the two lowest scores, and show what you changed.

[paste the draft]

Building your own tool

Turn an idea into a build brief (one AI prompts another)

When to use: Before you build a tool in Lovable or a similar builder.

I want to build [describe the tool in one or two sentences]. Interview me one question at a time to pull out the inputs, the outputs, the edge cases, and the data it needs and where that data lives. When you have enough, write a clear, structured build brief I can paste into an app builder. Do not start building; just write the brief.
Back to the companion site