Prompt libraryWork and business
Meetings, plans, customer messages and reports, with checks that keep invented details out.
Work prompts should say who the audience is, what decision the document supports and what facts the assistant may use. Without that, the output reads like every other business document.
Do not paste confidential or customer data into tools that your employer has not approved, and remember that free tiers can have different data terms than business plans.
From these meeting notes, list decisions made, action items with owner and due date (write "unassigned" if missing), and open questions. Do not invent owners or dates.
[paste notes]Why it works. Forbidding invention keeps actions honest.
Then check. Confirm owners and dates with the team.
Draft a one-page plan for [project]. Sections: goal, why now, scope, out of scope, milestones with rough dates, risks, and what I need from others. Ask me up to five questions first if information is missing.Why it works. Questions first avoids a generic plan.
Then check. Replace placeholder dates and owners with real ones.
A customer wrote:
[paste]
Our policy is: [policy]. Draft a short, friendly reply that answers their question, makes no promises beyond the policy, and offers one next step.Why it works. Grounding in your policy prevents promises you cannot keep.
Then check. Read for accuracy before sending; a person should send it.
Assume this project failed in six months: [project description]. List the ten most likely reasons, ranked, and one early warning sign and one mitigation for each.Why it works. Imagining failure surfaces risks that optimism hides.
Then check. Discard generic risks; keep the ones that fit your context.
Write a job post for [role] at a [type of company]. Separate must-haves from nice-to-haves, state the real salary range [range], and avoid unnecessary jargon or biased phrasing. List anything that might discourage qualified applicants unnecessarily.Why it works. Separating requirements widens the pool; stating pay builds trust.
Then check. Have HR or legal check it.
From the policy text below, write 8 customer FAQs with short answers. Use only what the text says; if the text doesn't answer a likely question, list it under "Needs an answer".
[paste policy]Why it works. The "needs an answer" list shows gaps in your policy.
Then check. Have the policy owner approve each answer.
Turn these bullets into a weekly update for [audience]: what shipped, what is next, blockers, and one thing I need help with. Keep it under 150 words.
[paste bullets]Why it works. A fixed structure makes updates fast to write and read.
Then check. Confirm nothing is overstated.