Copy-ready prompts, not a raw Markdown wall.

Turn this goal into a clear outcome, constraints, success criteria, and the next three actions: [GOAL]. Mark missing information instead of inventing it.

Summarize the material below in five bullets. Then list decisions, risks, assumptions, and open questions: [TEXT].

Turn this process into a practical checklist with an owner, required input, completion test, and failure note for each step: [PROCESS].

Compare these options by cost, effort, risk, reversibility, time-to-value, and likely benefit. State what information is missing before recommending a choice: [OPTIONS].

Draft a standard operating procedure for [TASK]. Include purpose, scope, inputs, ordered steps, review points, approval points, handoff notes, and a simple quality check.

Organize these notes into decisions, action items, owners, deadlines, blocked items, follow-up questions, and anything needing approval: [NOTES].

Review this page or document for plain language, heading structure, keyboard usability, contrast concerns, alt-text needs, mobile readability, and unnecessary complexity: [CONTENT].

What questions should be answered before we build, publish, buy, or commit to this? Group them by user need, product value, technical risk, legal risk, operations, and cost: [IDEA].

Create a research plan for [TOPIC]. Include source types, search terms, verification steps, comparison criteria, and a concise final-deliverable format.

Explain [CONCEPT] in plain language. Give one example, one non-example, three common mistakes, and three questions that check understanding.

Group this feedback into bugs, content changes, design changes, feature requests, risks, and questions. Rank the resulting work by urgency and effort: [FEEDBACK].

Create a conservative launch checklist for [PRODUCT / SERVICE]. Separate must-have, should-have, later, go/no-go criteria, and rollback actions.

Draft a short, respectful email explaining [SITUATION]. Use only the facts supplied, do not overpromise, and end with one clear next step: [FACTS].

Create an outline for a useful article, post, or guide about [TOPIC]. Include audience, promise, sections, examples, proof points, and a clear limitation.

Review this workflow for unclear ownership, missing approvals, privacy risk, handoff risk, failure points, and unnecessary manual work: [WORKFLOW].

List every assumption in this proposal. Mark each confirmed, likely, uncertain, risky, or unsafe to assume. Name the five assumptions to verify first: [PROPOSAL].

Create a handoff brief with context, current state, files or links, decisions made, unresolved questions, risks, and the exact next action: [PROJECT].

Write a manual test plan for this user path. Include happy path, empty state, error state, mobile behavior, accessibility checks, and rollback concerns: [PATH].

Rewrite this service description so it clearly states who it helps, what is included, what it does not promise, what proof supports it, and the next step: [DRAFT].

Before automating this task, identify the human decision, data needed, failure cost, approval point, safest small pilot, and what should remain human: [TASK].

Extract explicit requirements, goals, constraints, assumptions, unresolved questions, and out-of-scope items from this material: [MATERIAL]. Do not silently turn assumptions into requirements.

Create a short decision memo for [DECISION]. Include options, evidence, assumptions, tradeoffs, recommendation, reversible next step, and what would change the recommendation.

Create a practical risk register for [PROJECT]. For each risk list trigger, impact, likelihood evidence, mitigation, owner, and a verification step.

Convert this product idea into user stories grouped by user role. Keep each story tied to an observable user need and add one acceptance check: [IDEA].

Review these claims and label each SUPPORTED, UNSUPPORTED, CONFLICTING, or NEEDS VERIFICATION based only on the supplied sources. Do not fill gaps from memory: [CLAIMS + SOURCES].