Review-first run
Use this lesson plan workflow when the raw material is grade level, learning objective, standard, time limit, materials, and classroom. It turns that material into a sequenced plan with stages, owners, timing, and choice checkpoints and keeps classroom evidence, grade level, learning objective, and school rules in front of the person checking the answer.
Turn grade level, learning objective, standard, time limit, materials, and classroom constraints into a lesson plan for students, families, and school reviewers.
- Bring first
- Topic is thermal energy. Need bell ringer, quick demo, partner practice, exit ticket, and no materials beyond cups, warm water, ice, and thermometers. objective-to-activity map needs the source note, output shape, and review owner in the same pass. The answer should carry the user's boundary into the final sections. a lesson plan should use the note as its source. Before teachers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
Use this worksheet workflow when the raw material is topic, grade level, sample problems, answer expectations, and accommodation needs. It turns that material into a worksheet or practice set with copy-ready parts, needs-checking parts and keeps classroom evidence, grade level, learning objective, and school rules in front of the person checking the answer.
Turn topic, grade level, sample problems, answer expectations, and accommodation needs into a worksheet or practice set for students, families, and school reviewers.
- Bring first
- Make 12 questions, three easy visual questions, five mixed practice questions, two word problems, two challenge items, and a short answer key. practice ladder with answer checks needs the source note, output shape, and review owner in the same pass. The answer should carry the user's boundary into the final sections. a worksheet or practice set should use the note as its source. Before teachers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
The quiz prompt path asks for unit topics, difficulty range, question types, and answer key rules, creates a quiz with an answer key, and marks what still needs a person. It is meant for students, families, and school reviewers, not for one-click publishing.
Turn unit topics, difficulty range, question types, and answer key rules into a quiz with an answer key for students, families, and school reviewers.
- Bring first
- Topic is ratios and equivalent rates. Need 10 questions, three visual, four computation, two word problems, one challenge, plus answer key and common misconception notes. Teachers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The first answer should make the review path obvious. students, families, and school reviewers should still see the note while a quiz with an answer key is being built. Write Quizzes works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
Start with this material: assignment goal, performance levels, criteria, point weights, and examples of. Use the scoring rubric workflow to create a scoring rubric, keep criterion row with level anchors visible, add reject rules, and show students, families, and school reviewers what to check next.
Turn assignment goal, performance levels, criteria, point weights, and examples of strong work into a scoring rubric for students, families, and school reviewers.
- Bring first
- Assignment is one persuasive paragraph. Need 4 criteria, 4 performance levels, student-friendly wording, point values, and one example of evidence for each level. Phrase shopping fails for scoring rubric work because the note should become criterion row with level anchors. The user's note should stay readable after the answer is organized. This scoring rubric work run should turn that note into a scoring rubric. For scoring rubric work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a scoring table with levels, observable evidence, and reviewer notes.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
The parent email workflow turns rough notes into a parent email around neutral family communication, requested action, meeting context, and privacy-safe. It includes a sample run, rerun instruction, and reusable fields for the next pass.
Turn student-neutral context, meeting goal, requested action, tone, and privacy limits into a parent email for students, families, and school reviewers.
- Bring first
- Need subject line, short email, neutral tone, mention three missing assignments, ask for a 10-minute call, avoid blame, no private student comparison. Phrase shopping fails for parent email work because the note should become message version with meeting ask and privacy-safe wording. A safer answer should separate source notes from guesses. This parent email work run should turn that note into a parent email. For parent email work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a ready-to-edit message with subject line, body, tone notes, and review checklist.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
Use this when report card comments has real source material but still needs review. The page turns strengths, growth areas, classroom evidence, next step, and district tone into report card comments and shows what to keep, question, revise, or discard.
Turn strengths, growth areas, classroom evidence, next step, and district tone rules into report card comments for students, families, and school reviewers.
- Bring first
- Need two strengths, one growth area, one next step for home, positive tone, no labels, no sensitive details, about 75 words. In report card comments work, the rough note has to lead because role-level advice would flatten the situation. A reviewer needs those notes kept separate from assumptions. Carry the source note into report card comments. For report card comments work, paste the source as bullets, constraints, and audience notes so the model has enough shape for report card comments organized by context, output, caveats, and the next human action.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
Repeat classroom activity plan work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for classroom activity plan quality, grouping and facilitation moves.
Turn lesson goal, group size, time box, materials, movement limits, and wrap-up task into a classroom activity plan for students, families, and school reviewers.
- Bring first
- Need activity with pairs, one short shared text, movement optional, quick model, independent check, and exit ticket. Avoid requiring devices. Teachers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. students, families, and school reviewers should still see the note while a classroom activity plan is being built. Plan Classroom Activities works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Use this differentiation plan workflow when teachers need to move from source notes to a shareable answer without losing the original limits. It keeps differentiation plan quality, support options and skill target visible before reuse.
Turn student needs, target skill, available supports, grouping plan, and assessment method into a differentiation plan for students, families, and school reviewers.
- Bring first
- Goal is compare fractions with unlike denominators. Need three support levels, same core objective, vocabulary support, extension task, and quick check. support matrix by learner need would be weak without the source details, so the evidence has to stay attached. The response should make the source note easier to verify. Teachers should use the note as the base for a differentiation plan. Before teachers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about classroom evidence, grade level, learning objective, and school rules or treats uncertainty as fact.
Review-first run
Turn exam date, course topics, weak areas, available study blocks into a study plan with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks study plan quality, time blocks and topic priority before reuse.
Turn exam date, course topics, weak areas, available study blocks, and energy constraints into a study plan for the student, instructor, or academic advisor.
- Bring first
- I can study 60 minutes on weekdays, 2 hours Saturday, no Sunday morning, need active recall and practice questions, not rereading. Examples for study plan work help only when they keep the source note visible while shaping calendar block plan with weak-topic flags. The reusable version should keep this case as evidence. In study plan work, the supplied note becomes the base for a study plan. A usable starting note for study plan work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Use this workflow when the flashcard set job starts with source notes, definitions, formulas, examples, and recall difficulty and needs a clear output shape. The result can be checked before it reaches the student, instructor, or academic advisor.
Turn source notes, definitions, formulas, examples, and recall difficulty into a flashcard set for the student, instructor, or academic advisor.
- Bring first
- Use my notes only. Need 20 cards, mix definitions, cloze, compare questions, and two application cards. Mark uncertain facts for checking. In flashcard set work, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the source note into a flashcard set. For flashcard set work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a flashcard set with a source-backed outline, choice notes, and a closing check.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
The organized lecture notes prompt path asks for raw notes or transcript, course context, missing sections, and exam, creates organized lecture notes, and marks what still needs a person. It is meant for the student, instructor, or academic advisor, not for one-click publishing.
Turn raw notes or transcript, course context, missing sections, and exam relevance into organized lecture notes for the student, instructor, or academic advisor.
- Bring first
- Summarize into headings, key terms, possible exam questions, gaps I need to ask about, and a 15-minute review plan. Do not invent missed definitions. Students need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A safer first pass should expose the factual base. the student, instructor, or academic advisor should still see the note while organized lecture notes is being built. Summarize Lecture Notes works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
Repeat essay outline work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for essay outline quality, thesis logic and paragraph claims.
Turn assignment prompt, thesis idea, sources, required structure, and citation style into an essay outline for the student, instructor, or academic advisor.
- Bring first
- Need thesis options, four body paragraph claims, where to use each source, one counterargument, and questions I should answer myself. Students need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The answer should preserve the real case before improving wording. the student, instructor, or academic advisor should still see the note while an essay outline is being built. Plan an Essay Outline works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Start with this material: test format, topic list, weak spots, time remaining, and practice. Use the exam prep plan workflow to create an exam prep plan, keep practice plan with topic confidence bands visible, add reject rules, and show the student, instructor, or academic advisor what to check next.
Turn test format, topic list, weak spots, time remaining, and practice question needs into an exam prep plan for the student, instructor, or academic advisor.
- Bring first
- Need a six-day plan, 45 minutes weekdays, 2 hours Saturday, daily active recall, practice problems, and a way to review mistakes. Phrase shopping fails for exam prep plan work because the note should become practice plan with topic confidence bands. The user's note should stay readable after the answer is organized. This exam prep plan work run should turn that note into an exam prep plan. For exam prep plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and choice checkpoints.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
The research paper plan prompt path asks for research question, source list, thesis direction, method, and citation requirements, creates a research paper plan, and marks what still needs a person. It is meant for the student, instructor, or academic advisor, not for one-click publishing.
Turn research question, source list, thesis direction, method, and citation requirements into a research paper plan for the student, instructor, or academic advisor.
- Bring first
- Need research question refinement, source map, possible thesis, section outline, evidence gaps, and questions to take to office hours. Students need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The first answer should make the review path obvious. the student, instructor, or academic advisor should still see the note while a research paper plan is being built. Plan a Research Paper works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
The internship outreach email workbench starts with the notes you already have, then shapes them into a ready-to-edit message with subject line, body, tone notes. It is built for students who need outreach email with support line and ask, clear limits, and a reusable second pass.
Turn target company, role, connection point, experience support, and requested next step into an internship outreach email for the student, instructor, or academic advisor.
- Bring first
- Need subject line and 120-word email. Mention shared university, interest in operations analytics, one project, and ask for 15-minute advice call. Examples for internship outreach email work help only when they keep the source note visible while shaping outreach email with supporting line and ask. The working prompt should keep this as the factual base. In internship outreach email work, the supplied note becomes the base for an internship outreach email. A usable starting note for internship outreach email work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Use this active recall page when the job is an active recall practice set, not broad advice. It gives source prep, examples, prompts, and a short review path for active recall practice set quality, retrieval questions and self-check.
Turn topic list, source notes, difficulty level, and answer-check method into an active recall practice set for the student, instructor, or academic advisor.
- Bring first
- Use my muscle list and notes. Create recall questions, hide answers first, mix identification and function, and give a missed-question log format. retrieval practice set with answer checks needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. an active recall practice set should use the note as its source. Before students run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Review-first run
Turn role history, measurable outcomes, tools, scope, and target job description into resume bullets with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks resume bullets quality, achievement framing and measurable scope before reuse.
Turn role history, measurable outcomes, tools, scope, and target job description into resume bullets for a recruiter, hiring manager, or networking contact.
- Bring first
- Old bullet: helped with tickets and trained people. Need bullets for SaaS customer success role, no fake numbers, can mention Zendesk and onboarding. Examples for resume bullets work help only when they keep the source note visible while shaping bullet rewrite table with metric slots. The response should leave the source trail easy to inspect. In resume bullets work, the supplied note becomes the base for resume bullets. A usable starting note for resume bullets work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Use this cover letter workflow when the raw material is target role, company reason, relevant support, career story, and tone. It turns that material into a ready-to-edit message with subject line, body, tone notes and keeps true experience, measurable support, and target role fit in front of the person checking the answer.
Turn target role, company reason, relevant support, career story, and tone preference into a cover letter for a recruiter, hiring manager, or networking contact.
- Bring first
- I managed scheduling, inventory counts, and shift handoffs. Want to sound analytical without pretending I already worked as an analyst. paragraph map tied to the target role needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a cover letter should use the note as its source. Before job seekers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
The LinkedIn summary workbench starts with the notes you already have, then shapes them into a LinkedIn summary with field labels, short bullets, and a. It is built for job seekers who need profile summary with support and keyword lines, clear limits, and a reusable second pass.
Turn target audience, career themes, supporting details, keywords, and voice into a LinkedIn summary for a recruiter, hiring manager, or networking contact.
- Bring first
- Mention onboarding, ticket triage, Zendesk, coaching two teammates, customer empathy, and target CSM role. No fake metrics or buzzwords. Examples for LinkedIn summary work help only when they keep the source note visible while shaping profile summary with support and keyword lines. The working prompt should keep this as the factual base. In LinkedIn summary work, the supplied note becomes the base for a LinkedIn summary. A usable starting note for LinkedIn summary work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Review-first run
Use the interview answer practice page for a field-style example, runnable prompts, revision instructions, and checks for true experience, measurable support, and target role fit. It keeps the result close to job description, resume notes, likely concerns, and interview format.
Turn job description, resume notes, likely concerns, and interview format into interview answer practice for a recruiter, hiring manager, or networking contact.
- Bring first
- Need questions about failure, cross-functional conflict, metrics, and prioritization. Also need one STAR answer outline, not a script to memorize. Examples for interview answer practice work help only when they keep the source note visible while shaping answer bank with risk and support notes. A careful pass should keep the user's limit visible. In interview answer practice work, the supplied note becomes the base for interview answer practice. A usable starting note for interview answer practice work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
This STAR interview stories workflow is for job seekers who already have situation, task, action, result, lesson learned, and target competency and need STAR interview stories with named sections, action bullets, and a. It keeps the source, audience, review step, and handoff in one place.
Turn situation, task, action, result, lesson learned, and target competency into STAR interview stories for a recruiter, hiring manager, or networking contact.
- Bring first
- Situation was delayed shipment. I coordinated support, sales, and warehouse, gave daily updates, saved relationship. Need STAR outline, not a script. STAR story table with result evidence would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. Job Seekers should use the note as the base for STAR interview stories. Before job seekers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about true experience, measurable support, and target role fit or treats uncertainty as fact.
Ready-to-run path
Repeat salary negotiation plan work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for salary negotiation plan quality, value support and tradeoff list.
Turn offer details, market evidence, priorities, constraints, and fallback options into a salary negotiation plan for a recruiter, hiring manager, or networking contact.
- Bring first
- Offer is 74k, target is 80k, can trade for signing bonus or review at 6 months. Need email and talking points, respectful tone. Job Seekers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a recruiter, hiring manager, or networking contact should still see the note while a salary negotiation plan is being built. Plan Salary Negotiation works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
Repeat follow-up email work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for follow-up email quality, interview recap and hiring timeline.
Turn interview notes, recruiter name, hiring timeline, role interest, and one promised follow-up item into a follow-up email for a recruiter, hiring manager, or networking contact.
- Bring first
- Need thank-you email, mention process improvement discussion, attach sample dashboard, restate interest, ask about timeline lightly. Job Seekers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a recruiter, hiring manager, or networking contact should still see the note while a follow-up email is being built. Send Follow-up Emails works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Move from a rough career change request to a career-change explanation with the usable answer first, then gaps with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn past experience, new target role, transferable support, and credibility gaps into a career-change explanation for a recruiter, hiring manager, or networking contact.
- Bring first
- Past work: scheduling, shrink reports, inventory counts, staff handoffs. Target: operations analyst. Need honest narrative and supporting details. The first human check for career-change explanation work has to compare the answer with the supplied note. The response should keep the actual request visible through the edit. Start the career-change explanation from the rough request before shaping a career-change explanation. A usable starting note for career-change explanation work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Review-first run
Use the campaign brief page for a field-style example, runnable prompts, revision instructions, and checks for the user's notes, specific examples, constraints, and reviewer judgment. It keeps the result close to offer, audience, channel, support, timing, budget, and success metric.
Turn offer, audience, channel, support, timing, budget, and success metric into a campaign brief for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Audience is finance directors, offer is webinar, support is customer quote and benchmark report, channels are email, LinkedIn, and retargeting. Examples for campaign brief work help only when they keep the source note visible while shaping brief table with offer, audience, support, and channel. The response should not turn the case into broad advice. In campaign brief work, the supplied note becomes the base for a campaign brief. A usable starting note for campaign brief work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
The ad copy options workbench starts with the notes you already have, then shapes them into copy options grouped by angle, audience, support point, and revision. It is built for marketers who need claim-to-support copy matrix, clear limits, and a reusable second pass.
Turn product promise, audience pain, support, channel limits, and compliance constraints into ad copy options for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need five hooks, three body options under 150 characters, no fearmongering, mention checklist download, use practical tone. Examples for ad copy options work help only when they keep the source note visible while shaping claim-to-support copy matrix. The first pass should name the source details it is using. In ad copy options work, the supplied note becomes the base for ad copy options. A usable starting note for ad copy options work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Start the landing page copy run with the working case, then copy prompts that preserve hero promise, section order, objection handling, support blocks. The review pass checks notes from the user, example fit, constraints, and reviewer before anything gets reused.
Turn offer, visitor intent, support, objections, sections, and call to action into landing page copy for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need hero, pain bullets, how it works, support, FAQ, CTA. Tone calm and direct. Avoid promising tax advice. In landing page copy work, the rough note has to lead because role-level advice would flatten the situation. The working copy should expose what is known and unknown. Carry the source note into landing page copy. For landing page copy work, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, supporting detail, and revision note.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
Repeat email sequence work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for email sequence quality, send logic and segment trigger.
Turn list segment, trigger, offer, timing, objections, and conversion goal into an email sequence for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need 5 emails over 14 days, practical tone, trigger is no teammate invite, include product tip, support, objection, and soft CTA. Marketers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The answer should preserve the real case before improving wording. a campaign owner, creative reviewer, or channel manager should still see the note while an email sequence is being built. Plan Email Sequences works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Use this workflow when the customer persona job starts with research notes, behaviors, pains, buying triggers, objections, and language and needs a clear output shape. The result can be checked before it reaches a campaign owner, creative reviewer, or channel manager.
Turn research notes, behaviors, pains, buying triggers, objections, and language into a customer persona for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need persona segments from interview notes, pains, buying triggers, objections, language quotes, and evidence gaps. Do not invent age or salary. In customer persona work, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the source note into a customer persona. For customer persona work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a structured analysis table with claims, evidence, gaps, and recommended next step.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
Marketers get content calendar prompts that carry source context, example inputs, answer checks, and safe-use notes. The page keeps calendar row with channel, angle, and owner as the thing to inspect.
Turn audience, themes, dates, formats, channel mix, and campaign priorities into a content calendar for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need 4 weeks, LinkedIn, newsletter, blog, repurposing ideas, owner per asset, due dates, and what support each post uses. a campaign owner, creative reviewer, or channel manager can be misled by polished wording, so the reviewer check needs to stay visible. The prompt should make the reviewer questions unavoidable. Treat the rough request as first-pass evidence for a content calendar. Build Content Calendars works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Review-first run
Use this when competitor analysis has real source material but still needs review. The page turns competitor ads, landing pages, campaign claims, audience promise, and channel into a competitor analysis and shows what to keep, question, revise, or discard.
Turn competitor ads, landing pages, campaign claims, audience promise, and channel examples into a competitor analysis for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need table for competitor promise, target audience, support type, missing claims, pricing cue, and how our angle could differ. In competitor analysis work, the rough note has to lead because role-level advice would flatten the situation. A reviewer needs those notes kept separate from assumptions. Carry the source note into a competitor analysis. For competitor analysis work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a structured analysis table with claims, evidence, gaps, and recommended next step.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
The positioning statement workflow turns rough notes into a positioning statement around category choice, alternative options, differentiated support, and promise clarity. It includes a sample run, rerun instruction, and reusable fields for the next pass.
Turn target customer, alternative options, differentiated support, category, and promise into a positioning statement for a campaign owner, creative reviewer, or channel manager.
- Bring first
- Need positioning options, target customer, alternatives, differentiated support, tagline directions, and risks for each angle. Phrase shopping fails for positioning statement work because the note should become positioning statement with alternative and support. A safer answer should separate source notes from guesses. This positioning statement work run should turn that note into a positioning statement. For positioning statement work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a positioning statement with a source-backed outline, choice notes, and a closing check.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Review-first run
The keyword cluster plan prompt set keeps a keyword cluster plan, intent clusters, source data caveats, page mapping, and priority, and the final check tied to the same source note. It is built to reduce polished but unsupported answers.
Turn seed keywords, search performance data, page list, intent notes, and business priority into a keyword cluster plan for a search user, editor, or SEO lead.
- Bring first
- Need clusters, intent labels, suggested page type, cannibalization notes, and priority. Do not make up volume or rankings. keyword cluster table with page intent needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a keyword cluster plan should use the note as its source. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
Move from a rough content brief request to a content brief with named sections, action bullets, runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn main search phrase, search result notes, audience, angle, outline, and internal links into a content brief for a search user, editor, or SEO lead.
- Bring first
- Need H2 outline, search intent, must-answer questions, internal links, metadata angle, and what not to claim without local pricing data. The first human check for content brief work has to compare the answer with the supplied note. A useful version should keep the task boundary visible. Start the content brief from the rough request before shaping a content brief. A usable starting note for content brief work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
Use this when title tag options has real source material but still needs review. The page turns page topic, primary keyword, search intent, brand rule, and character into title tag options and shows what to keep, question, revise, or discard.
Turn page topic, primary keyword, search intent, brand rule, and character target into title tag options for a search user, editor, or SEO lead.
- Bring first
- Need 10 options for water heater repair page, primary query near front, under 60 characters if possible, no fake 24/7 claim. In title tag options work, the rough note has to lead because role-level advice would flatten the situation. A reviewer needs those notes kept separate from assumptions. Carry the source note into title tag options. For title tag options work, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, supporting detail, and revision note.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
This meta description options workflow is for seo specialists who already have page value, main search phrase, call to action, intent and need copy options grouped by angle, audience, support point, and revision. It keeps the source, audience, review step, and handoff in one place.
Turn page value, main search phrase, call to action, intent, and length constraint into meta description options for a search user, editor, or SEO lead.
- Bring first
- Need options around 150 characters, include who the page helps, avoid best/guaranteed claims, and mention comparison criteria. description variants with value and limit checks would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. SEO Specialists should use the note as the base for meta description options. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about real search data, visible page content, and query intent or treats uncertainty as fact.
Ready-to-run path
Start the internal linking plan run with the working case, then copy prompts that preserve target URL priority, anchor context, crawl depth, and topical. The review pass checks real search data, visible page content, and query intent before anything gets reused.
Turn site sections, destination pages, anchor ideas, page priority, and crawl constraints into an internal linking plan for a search user, editor, or SEO lead.
- Bring first
- Use page list with URLs, target pages, current anchors, and intent notes. Need link opportunities, anchor suggestions, and cannibalization warnings. In internal linking plan work, the rough note has to lead because role-level advice would flatten the situation. The working copy should expose what is known and unknown. Carry the source note into an internal linking plan. For internal linking plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for an internal linking plan organized by context, output, caveats, and the next human action.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
Use this content refresh brief page when the job is a content refresh brief, not broad advice. It gives source prep, examples, prompts, and a short review path for content refresh brief quality, stale sections and ranking loss.
Turn current page copy, performance data, search result changes, stale facts, and conversion goal into a content refresh brief for a search user, editor, or SEO lead.
- Bring first
- Need refresh brief from current page, GSC queries, competitor notes, outdated claims, internal links, and what not to change. refresh brief with stale-section notes needs the source note, output shape, and review owner in the same pass. A practical answer should keep the handoff choice visible. a content refresh brief should use the note as its source. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Review-first run
SEO Specialists can move from top result pages, result types, query modifiers, user intent clues to a search result intent analysis without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for search result intent analysis quality, result type mix and intent.
Turn top result pages, result types, query modifiers, user intent clues, and content gaps into a search result intent analysis for a search user, editor, or SEO lead.
- Bring first
- Need result type summary, recurring sections, PAA themes, missing support, local intent clues, and content risks. No volume or rank claims. search results pattern table with page-type gaps would be weak without the source details, so the evidence has to stay attached. A usable first pass has to preserve those constraints. SEO Specialists should use the note as the base for a search result intent analysis. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about real search data, visible page content, and query intent or treats uncertainty as fact.
Ready-to-run path
Use this workflow when the schema markup plan job starts with page type, visible content, entity details, required properties, and validation and needs a clear output shape. The result can be checked before it reaches a search user, editor, or SEO lead.
Turn page type, visible content, entity details, required properties, and validation target into a schema markup plan for a search user, editor, or SEO lead.
- Bring first
- Need schema recommendation, required fields, visible-content match check, JSON-LD example, and validation checklist. Do not invent reviews. In schema markup plan work, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the source note into a schema markup plan. For schema markup plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a schema markup plan organized by context, output, caveats, and the next human action.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
Sales Reps get a runnable cold email setup with sample notes, copyable prompts, and a review pass for cold email quality, account trigger and pain hypothesis. It is strongest when the weak spot is outreach can look personalized while relying on a guessed trigger.
Turn account trigger, prospect role, pain hypothesis, support, and requested action into a cold email for a prospect, buyer committee, or sales manager.
- Bring first
- Need subject lines and one 90-word email. Use trigger from job post, mention scheduling complexity, no fake personalization. The first human check for cold email work has to compare the answer with the supplied note. A practical prompt should keep the missing details visible. Start the cold email from the rough request before shaping a cold email. A usable starting note for cold email work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
Use this LinkedIn outreach message workflow when the raw material is profile context, shared relevance, reason for contact, and low-friction ask. It turns that material into a ready-to-edit message with subject line, body, tone notes and keeps true experience, measurable support, and target role fit in front of the person checking the answer.
Turn profile context, shared relevance, reason for contact, and low-friction ask into a LinkedIn outreach message for a prospect, buyer committee, or sales manager.
- Bring first
- Need connection note under 250 characters and follow-up message. Mention public post, ask about cleanup process, no fake shared contacts. connection note with relevance support needs the source note, output shape, and review owner in the same pass. The answer should carry the user's boundary into the final sections. a LinkedIn outreach message should use the note as its source. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
The discovery questions setup gives sales reps a working prompt pack backed by real notes, clear limits, and reviewable output. It centers question ladder by buyer signal, not generic advice.
Turn buyer role, suspected problem, deal stage, product fit, and learning goal into discovery questions for a prospect, buyer committee, or sales manager.
- Bring first
- Need questions by theme: current process, incidents, budget, stakeholders, timeline, and disqualification. Keep conversational. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat the rough request as first-pass evidence for discovery questions. Prepare Discovery Questions works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Review-first run
Move from a rough objections request to an objection-handling response with copy-ready parts, needs-checking parts, and reuse with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn objection wording, buyer context, support, tradeoff, and next commitment into an objection-handling response for a prospect, buyer committee, or sales manager.
- Bring first
- Need response options for implementation concern, discovery follow-ups, supporting details to request, and when to pause the deal. The first human check for objection-handling response work has to compare the answer with the supplied note. A useful version should keep the task boundary visible. Start the objection-handling response from the rough request before shaping an objection-handling response. A usable starting note for objection-handling response work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
Use this follow-up email workflow when sales reps need to move from source notes to a shareable answer without losing the original limits. It keeps follow-up email quality, buyer commitment and objection recap visible before reuse.
Turn sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal into a follow-up email for a prospect, buyer committee, or sales manager.
- Bring first
- Need follow-up email with recap, two pains, promised case study, next meeting ask, and no pressure language. follow-up note with promised item and timing would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Sales Reps should use the note as the base for a follow-up email. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about verified account context, buyer language, and deal stage or treats uncertainty as fact.
Ready-to-run path
Move from company page, recent signals, role map, pain hypothesis, and source to a structured analysis table with claims, evidence, gaps, and recommended with the account research summary workbench. It keeps assumptions, constraints, and the person checking the answer visible while you work.
Turn company page, recent signals, role map, pain hypothesis, and source links into an account research summary for a prospect, buyer committee, or sales manager.
- Bring first
- Need account brief with public triggers, possible hypotheses, questions to validate, stakeholders, and risks. Label assumptions clearly. The first human check for account research summary work has to compare the answer with the supplied note. The output should carry the user's limits into every section. Start the account research summary from the rough request before shaping an account research summary. A usable starting note for account research summary work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Review-first run
Move from a rough call summary request to a call summary with copy-ready parts, needs-checking parts, and reuse with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn call notes, choices, objections, owners, dates, and follow-up commitments into a call summary for a prospect, buyer committee, or sales manager.
- Bring first
- Need summary with pain, current process, stakeholders, objections, success criteria, next steps, owner, and follow-up email bullets. The first human check for call summary work has to compare the answer with the supplied note. The response should keep the actual request visible through the edit. Start the call summary from the rough request before shaping a call summary. A usable starting note for call summary work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
The proposal outline setup gives sales reps a working prompt pack backed by real notes, clear limits, and reviewable output. It centers proposal section outline with scope and assumptions, not generic advice.
Turn client problem, scope, deliverables, timeline, support, assumptions, and pricing context into a proposal outline for a prospect, buyer committee, or sales manager.
- Bring first
- Need proposal outline, executive summary, scope, timeline, support, assumptions, risks, and next step. No made-up ROI. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat the rough request as first-pass evidence for a proposal outline. Write Proposals works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Review-first run
Start with this material: property facts, features, neighborhood context, photo notes, and compliance limits. Use the listing description workflow to create a listing description, keep listing copy map with fact-only feature notes visible, add reject rules, and show a buyer, seller, lead, or broker reviewer what to check next.
Turn property facts, features, neighborhood context, photo notes, and compliance limits into a listing description for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping fails for listing description work because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This listing description work run should turn that note into a listing description. For listing description work, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, supporting detail, and revision note.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
This buyer email workflow is for real estate agents who already have buyer criteria, listings discussed, timing, next step, and local constraints and need a ready-to-edit message with subject line, body, tone notes. It keeps the source, audience, review step, and handoff in one place.
Turn buyer criteria, listings discussed, timing, next step, and local constraints into a buyer email for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need short email comparing 3 homes, pros and tradeoffs, showing availability, next step, and no pressure tone. buyer note with criteria and next-tour action would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. Real Estate Agents should use the note as the base for a buyer email. Before real estate agents run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.
Ready-to-run path
Real Estate Agents get a runnable seller script setup with sample notes, copyable prompts, and a review pass for seller script quality, motivation discovery and pricing caveats. It is strongest when the weak spot is seller scripts can sound confident while market evidence and legal-sensitive boundaries are thin.
Turn seller motivation, property context, market data, concerns, and meeting goal into a seller script for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need script for pricing conversation, prep checklist, timeline, objections, and how to explain comps respectfully. The first human check for seller script work has to compare the answer with the supplied note. A practical prompt should keep the missing details visible. Start the seller script from the rough request before shaping a seller script. A usable starting note for seller script work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Review-first run
Turn visitor notes, property interest, objections, timing, and next action into open house follow-up messages with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks open house follow-up messages quality, visitor signal and property before reuse.
Turn visitor notes, property interest, objections, timing, and next action into open house follow-up messages for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need three follow-up versions: interested buyer, casual visitor, agent with buyer. Mention verified facts only and ask next step. Examples for open house follow-up messages work help only when they keep the source note visible while shaping visitor follow-up set by interest level. The reusable version should keep this case as evidence. In open house follow-up messages work, the supplied note becomes the base for open house follow-up messages. A usable starting note for open house follow-up messages work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
The neighborhood guide outline workflow turns rough notes into a neighborhood guide outline around amenity categories, commute context, lifestyle fit, and source caveats. It includes a sample run, rerun instruction, and reusable fields for the next pass.
Turn local amenities, commute notes, housing style, lifestyle fit, and source limits into a neighborhood guide outline for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need guide sections, data to verify, local amenities, commute notes, housing types, and fair housing safe language. Phrase shopping fails for neighborhood guide outline work because the note should become guide outline with source-limited local notes. The prompt should turn the note into checkable material. This neighborhood guide outline work run should turn that note into a neighborhood guide outline. For neighborhood guide outline work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a neighborhood guide outline with a source-backed outline, choice notes, and a closing check.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
This market update workflow is for real estate agents who already have local data source, timeframe, inventory, price trend, and caveats and need a market update split into reader-ready copy, open questions. It keeps the source, audience, review step, and handoff in one place.
Turn local data source, timeframe, inventory, price trend, and caveats into a market update for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need client-friendly update, explain what changed, what it means for buyers and sellers, include caveats, no prediction guarantees. market note with timeframe and caveat row would be weak without the source details, so the evidence has to stay attached. A strong response should keep the practical limits in view. Real Estate Agents should use the note as the base for a market update. Before real estate agents run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.
Review-first run
Move from a rough social posts request to copy options grouped by angle, audience, support point, and revision with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn listing or service angle, platform, audience, support, and compliance limits into social posts for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need 5 posts, each under 120 words, no fair housing issues, include CTA, and mark facts I must verify. The first human check for social posts work has to compare the answer with the supplied note. A useful version should keep the task boundary visible. Start the social posts from the rough request before shaping social posts. A usable starting note for social posts work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
Use the review reply flow to keep public reputation, property-service context, local compliance, and lead trust from disappearing in polished wording. The result is a review reply, plus checks for the actual notes, usable examples, boundary checks, and reviewer.
Turn review text, customer sentiment, service facts, tone, and escalation boundary into a review reply for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need public reply under 80 words, thank client, no private transaction details, mention trust and next-step referrals lightly. Phrase shopping fails for review reply work because the note should become reply version with escalation and public-tone limits. A stronger run should protect the user's real limits. This review reply work run should turn that note into a review reply. For review reply work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a ready-to-edit message with subject line, body, tone notes, and review checklist.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Review-first run
The business plan outline prompt set keeps a business plan outline, customer, offer, revenue logic, cost assumptions, and milestone risk, and the final check tied to the same source note. It is built to reduce polished but unsupported answers.
Turn business model, customer, offer, costs, channels, risks, and near-term milestone into a business plan outline for a customer, employee, applicant, or local buyer.
- Bring first
- Need sections for customers, offer, pricing assumptions, costs, operations, risks, milestones, and questions for accountant. No fake projections. plan outline with risk and milestone rows needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a business plan outline should use the note as its source. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
The local marketing plan prompt path asks for service area, customer segment, local channels, offer, budget, and calendar, creates a local marketing plan, and marks what still needs a person. It is meant for a customer, employee, applicant, or local buyer, not for one-click publishing.
Turn service area, customer segment, local channels, offer, budget, and calendar into a local marketing plan for a customer, employee, applicant, or local buyer.
- Bring first
- Need Google Business Profile ideas, email, flyers, referral offer, review ask, budget-light plan, and tracking notes. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The first answer should make the review path obvious. a customer, employee, applicant, or local buyer should still see the note while a local marketing plan is being built. Plan Local Marketing works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Use this customer service replies workflow when small business owners need to move from source notes to a shareable answer without losing the original limits. It keeps customer service replies quality, customer issue and policy boundary visible before reuse.
Turn customer message, order or service context, policy, tone, and resolution options into customer service replies for a customer, employee, applicant, or local buyer.
- Bring first
- Need response examples, tone rules, refund boundary, escalation trigger, and what staff should not promise. reply set with policy and resolution path would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Small Business Owners should use the note as the base for customer service replies. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.
Review-first run
Repeat sops work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for standard operating procedure quality, trigger and owner, and customer-ready.
Turn process trigger, owner, tool access, step order, exceptions, and quality checks into a standard operating procedure for a customer, employee, applicant, or local buyer.
- Bring first
- Need SOP with timing, supplies, responsible role, quality check, exception handling, and closing handoff note. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a customer, employee, applicant, or local buyer should still see the note while a standard operating procedure is being built. Write Sops works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Use this hiring post workflow when the raw material is role scope, required skills, schedule, compensation range, culture notes. It turns that material into a hiring post split into reader-ready copy, open questions and keeps the pasted notes, concrete examples, hard limits, and reviewer in front of the person checking the answer.
Turn role scope, required skills, schedule, compensation range, culture notes, and screening rules into a hiring post for a customer, employee, applicant, or local buyer.
- Bring first
- Need job post with duties, schedule, pay range note, must-haves, nice-to-haves, application steps, and inclusive wording. role post with scope and screening notes needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a hiring post should use the note as its source. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
Use this when review reply has real source material but still needs review. The page turns review text, customer sentiment, service facts, tone, and escalation boundary into a review reply and shows what to keep, question, revise, or discard.
Turn review text, customer sentiment, service facts, tone, and escalation boundary into a review reply for a customer, employee, applicant, or local buyer.
- Bring first
- Need public reply under 90 words, acknowledge wait, thank customer, invite direct contact, no excuses, no coupon promise. In review reply work, the rough note has to lead because role-level advice would flatten the situation. A useful handoff should preserve the evidence before improving tone. Carry the source note into a review reply. For review reply work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a ready-to-edit message with subject line, body, tone notes, and review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
The pricing page copy setup gives small business owners a working prompt pack backed by real notes, clear limits, and reviewable output. It centers pricing section copy with plan-fit checks, not generic advice. It also names the objection language a customer may raise about price, value, or plan fit.
Turn offer tiers, customer segment, support, objections, inclusions, and limits into pricing page copy for a customer, employee, applicant, or local buyer.
- Bring first
- Need package descriptions, who each fits, what is included, what costs extra, FAQ, and no tax or legal advice promise. a customer, employee, applicant, or local buyer can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat the rough request as first-pass evidence for pricing page copy. Write Pricing Pages works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Ready-to-run path
Bring audience segment, topic, offer, links, timing, and voice into the email newsletter workflow and keep audience segment, editorial hook, offer placement, and click path visible from the first run. small business owners can check email newsletter quality, audience segment and editorial hook before sharing the result.
Turn audience segment, topic, offer, links, timing, and voice into an email newsletter for a customer, employee, applicant, or local buyer.
- Bring first
- Need subject lines, intro, three tips, workshop CTA, product mention, and local weather caveat. Friendly but not too salesy. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The answer should start from the supplied details. a customer, employee, applicant, or local buyer should still see the note while an email newsletter is being built. Write Email Newsletters works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
Freelancers can move from client problem, scope, deliverables, timeline, support, assumptions, and pricing context to a proposal outline without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for proposal outline quality, client scope and deliverable boundary.
Turn client problem, scope, deliverables, timeline, support, assumptions, and pricing context into a proposal outline for a client, prospect, or project stakeholder.
- Bring first
- Need proposal with goals, scope, deliverables, timeline, client inputs, assumptions, out-of-scope items, and next step. proposal section outline with scope and assumptions would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Freelancers should use the note as the base for a proposal outline. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about verified account context, buyer language, and deal stage or treats uncertainty as fact.
Ready-to-run path
Freelancers can move from buyer role, suspected problem, deal stage, product fit, and learning to discovery questions without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for discovery questions quality, client goals and scope risk.
Turn buyer role, suspected problem, deal stage, product fit, and learning goal into discovery questions for a client, prospect, or project stakeholder.
- Bring first
- Need questions about audience, offer, current page, support, competitors, timeline, budget, approvals, and red flags. question ladder by buyer signal would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Freelancers should use the note as the base for discovery questions. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about true experience, measurable support, and target role fit or treats uncertainty as fact.
Ready-to-run path
Use this scope of work workflow when the raw material is client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules. It turns that material into a scope of work split into reader-ready copy, open questions and keeps the pasted notes, concrete examples, hard limits, and reviewer in front of the person checking the answer.
Turn client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules into a scope of work for a client, prospect, or project stakeholder.
- Bring first
- Need SOW sections, deliverables, client inputs, timeline, revision policy, exclusions, acceptance criteria, and change request language. scope table with exclusions and acceptance terms needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a scope of work should use the note as its source. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Review-first run
Start with this material: client goals, access needs, kickoff agenda, owners, and communication cadence. Use the client onboarding plan workflow to create a client onboarding plan, keep onboarding checklist with owner and access fields visible, add reject rules, and show a client, prospect, or project stakeholder what to check next.
Turn client goals, access needs, kickoff agenda, owners, and communication cadence into a client onboarding plan for a client, prospect, or project stakeholder.
- Bring first
- Need onboarding checklist, account access, brand assets, audience info, approvals, timeline, and first-week agenda. Phrase shopping fails for client onboarding plan work because the note should become onboarding checklist with owner and access fields. The user's note should stay readable after the answer is organized. This client onboarding plan work run should turn that note into a client onboarding plan. For client onboarding plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and choice checkpoints.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
The project update workflow turns rough notes into a project update around completed work, blocker, choice needed, timeline risk, and owner. It includes a sample run, rerun instruction, and reusable fields for the next pass.
Turn completed work, blockers, choices needed, next steps, and deadline risk into a project update for a client, prospect, or project stakeholder.
- Bring first
- Need update with completed work, current blocker, choice needed, next milestone, timeline impact, and friendly tone. Phrase shopping fails for project update work because the note should become status update with blocker and choice rows. A safer answer should separate source notes from guesses. This project update work run should turn that note into a project update. For project update work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a project update with copy-ready parts, needs-checking parts, and reuse fields.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
Bring customer context, problem, approach, evidence, outcome, and permission limits into the case study outline workflow and keep before state, intervention, evidence, outcome, and permission boundary visible from the first run. freelancers can check case study outline quality, before state and intervention before sharing the result.
Turn customer context, problem, approach, evidence, outcome, and permission limits into a case study outline for a client, prospect, or project stakeholder.
- Bring first
- Need case study outline with problem, approach, deliverables, client quote, visual support, limits, and CTA. No fake metrics. Freelancers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The model output should keep the rough request attached to each choice. a client, prospect, or project stakeholder should still see the note while a case study outline is being built. Write Case Studies works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
Use the testimonial request flow to keep relationship context, result prompt, approval path, and easy reply from disappearing in polished wording. The result is a testimonial request, plus checks for the actual notes, usable examples, boundary checks, and reviewer.
Turn client relationship, result achieved, timing, ask, and approval path into a testimonial request for a client, prospect, or project stakeholder.
- Bring first
- Need email ask, 4 guiding questions, short LinkedIn version, permission note, and gentle follow-up after one week. Phrase shopping fails for testimonial request work because the note should become request note with approval and quote boundary. The workbench should turn this note into checkable fields. This testimonial request work run should turn that note into a testimonial request. For testimonial request work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a testimonial request with copy-ready parts, needs-checking parts, and reuse fields.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
The pricing prompt set keeps a pricing explanation, cost drivers, value logic, tradeoffs, and scope protection, and the final check tied to the same source note. It is built to reduce polished but unsupported answers.
Turn service scope, value support, cost drivers, alternatives, and boundaries into a pricing explanation for a client, prospect, or project stakeholder.
- Bring first
- Need explanation for price, what is included, why it matters, payment schedule, alternatives, and boundary for extra work. pricing explanation with cost-driver rows needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a pricing explanation should use the note as its source. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Review-first run
Use this when debugging plan has real source material but still needs review. The page turns error message, reproduction steps, recent changes, environment, and expected behavior into a debugging plan and shows what to keep, question, revise, or discard.
Turn error message, reproduction steps, recent changes, environment, and expected behavior into a debugging plan for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need likely causes, questions to ask, reproduction plan, and commands to verify. Do not suggest random rewrites. In debugging plan work, the rough note has to lead because role-level advice would flatten the situation. A reviewer needs those notes kept separate from assumptions. Carry the source note into a debugging plan. For debugging plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a technical checklist with hypotheses, steps, risks, and verification commands.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
Turn diff summary, affected files, risk areas, tests, and intended behavior into a code review checklist with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks code review checklist quality, behavior risk and diff hotspots before reuse.
Turn diff summary, affected files, risk areas, tests, and intended behavior into a code review checklist for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need review checklist for security, redirects, edge cases, tests, naming, and rollback risk. Include questions for reviewer. Examples for code review checklist work help only when they keep the source note visible while shaping review checklist mapped to changed files. The response should leave the source trail easy to inspect. In code review checklist work, the supplied note becomes the base for a code review checklist. A usable starting note for code review checklist work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Start with this material: function behavior, edge cases, inputs, outputs, and existing test style. Use the unit test cases workflow to create unit test cases, keep test case table with edge conditions visible, add reject rules, and show a code reviewer, teammate, maintainer, or future self what to check next.
Turn function behavior, edge cases, inputs, outputs, and existing test style into unit test cases for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need test cases, names, assertions, and edge cases. Existing tests use Vitest. Avoid testing implementation details. Phrase shopping fails for unit test cases work because the note should become test case table with edge conditions. The user's note should stay readable after the answer is organized. This unit test cases work run should turn that note into unit test cases. For unit test cases work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a technical checklist with hypotheses, steps, risks, and verification commands.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Review-first run
Turn feature behavior, audience, setup steps, examples, and known limitations into developer documentation with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks developer documentation quality, reader task and setup path before reuse.
Turn feature behavior, audience, setup steps, examples, and known limitations into developer documentation for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need overview, setup steps, retry timing, example payload, error cases, limitations, and support troubleshooting notes. Examples for developer documentation work help only when they keep the source note visible while shaping doc outline with example and limitation blocks. The response should leave the source trail easy to inspect. In developer documentation work, the supplied note becomes the base for developer documentation. A usable starting note for developer documentation work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Use this workflow when the refactoring plan job starts with current code shape, pain points, behavior to preserve, tests and needs a clear output shape. The result can be checked before it reaches a code reviewer, teammate, maintainer, or future self.
Turn current code shape, pain points, behavior to preserve, tests, and migration risk into a refactoring plan for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need refactor plan, preserved behavior, test coverage, file moves, migration steps, risks, and verification commands. In refactoring plan work, the rough note has to lead because role-level advice would flatten the situation. A working result should keep source, limit, and reviewer together. Carry the source note into a refactoring plan. For refactoring plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a technical checklist with hypotheses, steps, risks, and verification commands.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
The API integration plan prompt path asks for API docs, auth model, endpoints, data shape, errors, and rate, creates an API integration plan, and marks what still needs a person. It is meant for a code reviewer, teammate, maintainer, or future self, not for one-click publishing.
Turn API docs, auth model, endpoints, data shape, errors, and rate limits into an API integration plan for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need integration plan from docs, endpoints, auth flow, data mapping, error handling, webhook validation, and tests. Developers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A safer first pass should expose the factual base. a code reviewer, teammate, maintainer, or future self should still see the note while an API integration plan is being built. Sketch API Integration works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Review-first run
The regex prompt path asks for target pattern, sample matches, sample non-matches, escaping rules, and test, creates a plain-language regex explanation, and marks what still needs a person. It is meant for a code reviewer, teammate, maintainer, or future self, not for one-click publishing.
Turn target pattern, sample matches, sample non-matches, escaping rules, and test cases into a plain-language regex explanation for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need regex explanation, pattern, sample matches, sample non-matches, edge cases, and test cases. Avoid catastrophic backtracking. Developers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A safer first pass should expose the factual base. a code reviewer, teammate, maintainer, or future self should still see the note while a plain-language regex explanation is being built. Explain Regex works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Developers can move from current skill level, target outcome, time budget, projects, and feedback to a learning roadmap without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for learning roadmap quality, skill baseline and project ladder.
Turn current skill level, target outcome, time budget, projects, and feedback loop into a learning roadmap for a code reviewer, teammate, maintainer, or future self.
- Bring first
- Need weekly plan, projects, reading, practice tasks, checkpoints, feedback sources, and what to skip. 5 hours per week. roadmap with practice project and feedback loop would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Developers should use the note as the base for a learning roadmap. Before developers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about actual error output, code behavior, and passing verification or treats uncertainty as fact.
Review-first run
Use this prds workflow when product managers need to move from source notes to a shareable answer without losing the original limits. It keeps product requirements document outline quality, problem framing and user visible before reuse.
Turn problem evidence, target users, scope boundaries, success metrics, risks, and open questions into a product requirements document outline for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need problem, users, goals, non-goals, user stories, metrics, risks, open questions, and acceptance criteria. PRD outline with choice and risk rows would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Product Managers should use the note as the base for a product requirements document outline. Before product managers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.
Ready-to-run path
Start with this material: user segment, job, pain, desired outcome, and acceptance signals. Use the user stories workflow to create user stories, keep story set with acceptance signals visible, add reject rules, and show a product team, stakeholder, customer researcher, or release what to check next.
Turn user segment, job, pain, desired outcome, and acceptance signals into user stories for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
Turn feature goal, edge cases, roles, data states, and failure behavior into acceptance criteria with a worked input, a copyable run, and a second pass for weak sections. The reviewer checks acceptance criteria quality, given-when-then states and edge cases before reuse.
Turn feature goal, edge cases, roles, data states, and failure behavior into acceptance criteria for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Review-first run
Bring initiatives, evidence, effort, dependencies, risk, and business goal into the roadmap prioritization table workflow and keep evidence strength, effort, dependency, risk, and sequencing visible from the first run. product managers can check roadmap prioritization table quality, evidence strength and effort before sharing the result.
Turn initiatives, evidence, effort, dependencies, risk, and business goal into a roadmap prioritization table for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need prioritization table with user evidence, business goal, effort, confidence, risk, dependency, and recommendation. Product Managers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The answer should start from the supplied details. a product team, stakeholder, customer researcher, or release owner should still see the note while a roadmap prioritization table is being built. Prioritize Roadmaps works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.
Ready-to-run path
Use the competitor analysis page for a field-style example, runnable prompts, revision instructions, and checks for the user's notes, specific examples, constraints, and reviewer judgment. It keeps the result close to competitor feature set, user workflow, pricing cues, roadmap signals.
Turn competitor feature set, user workflow, pricing cues, roadmap signals, and customer jobs into a competitor analysis for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need table for activation steps, friction, user promise, pricing gates, missing evidence, and opportunities. Use observed screens only. Examples for competitor analysis work help only when they keep the source note visible while shaping competitor comparison grid with evidence gaps. The response should not turn the case into broad advice. In competitor analysis work, the supplied note becomes the base for a competitor analysis. A usable starting note for competitor analysis work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
Use the release notes page for a field-style example, runnable prompts, revision instructions, and checks for the user's notes, specific examples, constraints, and reviewer judgment. It keeps the result close to changes shipped, affected users, benefits, known limits, and upgrade actions.
Turn changes shipped, affected users, benefits, known limits, and upgrade actions into release notes for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need release notes with user benefit, who is affected, what changed, setup action, known limitation, and support link. Examples for release notes work help only when they keep the source note visible while shaping release note version with user-impact rows. The response should not turn the case into broad advice. In release notes work, the supplied note becomes the base for release notes. A usable starting note for release notes work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Review-first run
The feedback synthesis page helps product managers turn rough notes into a feedback synthesis. It pairs the prompt with a concrete example, stop rules, and a next workflow when the task does not fit.
Turn feedback items, segments, frequency, severity, quotes, and product area into a feedback synthesis for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat the rough request as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Ready-to-run path
Use the customer interview guide page for a field-style example, runnable prompts, revision instructions, and checks for true experience, measurable support, and target role fit. It keeps the result close to research goal, participant segment, assumptions, questions, and follow-up plan.
Turn research goal, participant segment, assumptions, questions, and follow-up plan into a customer interview guide for a product team, stakeholder, customer researcher, or release owner.
- Bring first
- Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for customer interview guide work help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In customer interview guide work, the supplied note becomes the base for a customer interview guide. A usable starting note for customer interview guide work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Review-first run
Use this job description page when the job is a job description, not broad advice. It gives source prep, examples, prompts, and a short review path for job description quality, role outcomes and required skills.
Turn role outcomes, responsibilities, requirements, compensation range, and hiring process into a job description for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Ready-to-run path
Move from a rough interview questions request to interview questions with the usable answer first, then gaps with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn role scorecard, competencies, level, format, and fairness constraints into interview questions for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need competency groups, behavioral questions, follow-ups, scoring notes, and questions to avoid. Keep job-related and fair. The first human check for interview questions work has to compare the answer with the supplied note. The response should keep the actual request visible through the edit. Start the interview questions from the rough request before shaping interview questions. A usable starting note for interview questions work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
HR and Recruiters get product scorecard prompts that carry source context, example inputs, answer checks, and safe-use notes. The page keeps scorecard row with evidence examples as the thing to inspect.
Turn role criteria, rating levels, evidence examples, and interviewer notes into a product scorecard for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need criteria, 1-5 levels, evidence examples, interviewer notes, red flags, and calibration guidance. a candidate, employee, hiring panel, or HR reviewer can be misled by polished wording, so the reviewer check needs to stay visible. The prompt should make the reviewer questions unavoidable. Treat the rough request as first-pass evidence for a product scorecard. Build Interview Scorecards works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Review-first run
Use this workflow when the onboarding plan job starts with new hire role, first-week goals, tools, meetings, and success signals and needs a clear output shape. The result can be checked before it reaches a candidate, employee, hiring panel, or HR reviewer.
Turn new hire role, first-week goals, tools, meetings, and success signals into an onboarding plan for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need 30-day plan, first week schedule, tools, buddy, manager checkpoints, learning goals, and success criteria. In onboarding plan work, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the source note into an onboarding plan. For onboarding plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and choice checkpoints.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
Start the employee survey run with the working case, then copy prompts that preserve question neutrality, anonymity, scale wording, and actionability. The review pass checks notes from the user, example fit, constraints, and reviewer before anything gets reused.
Turn research goal, audience, sensitive topics, scale, and anonymity limits into an employee survey for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need 10 survey questions, mix scale and open text, anonymity note, sensitive wording review, and reporting caveats. In employee survey work, the rough note has to lead because role-level advice would flatten the situation. The answer should make the user's constraint hard to miss. Carry the source note into an employee survey. For employee survey work, paste the source as bullets, constraints, and audience notes so the model has enough shape for an employee survey with a source-backed outline, choice notes, and a closing check.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
The performance review prompts workbench starts with the notes you already have, then shapes them into performance review prompts with field labels, short bullets, and a. It is built for hr and recruiters who need review note with example and growth rows, clear limits, and a reusable second pass.
Turn role expectations, examples, growth areas, goals, and HR policy into performance review prompts for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need review prompts for accomplishments, collaboration, growth areas, goals, and manager evidence. Avoid personality judgments. Examples for performance review prompts work help only when they keep the source note visible while shaping review note with example and growth rows. The first pass should name the source details it is using. In performance review prompts work, the supplied note becomes the base for performance review prompts. A usable starting note for performance review prompts work includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Review-first run
The policy language page helps hr and recruiters turn rough notes into policy language. It pairs the prompt with a concrete example, stop rules, and a next workflow when the task does not fit.
Turn policy goal, audience, legal review notes, examples, and escalation path into policy language for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need policy sections, employee responsibilities, manager approval, equipment, security, exceptions, and review notes. a candidate, employee, hiring panel, or HR reviewer can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat the rough request as first-pass evidence for policy language. Write Policy Language works better when the context is in named fields, because each variable can be checked before copying.
- Reject if
- Discard the answer if it cannot trace which details came from the source and which details were inferred.
Ready-to-run path
Use this rejection email workflow when hr and recruiters need to move from source notes to a shareable answer without losing the original limits. It keeps rejection email quality, candidate stage and respectful tone visible before reuse.
Turn candidate stage, tone, relationship, feedback policy, and next opportunity into a rejection email for a candidate, employee, hiring panel, or HR reviewer.
- Bring first
- Need two rejection email versions, respectful tone, no legal risk, optional future interest line, and feedback-policy boundary. rejection note set with feedback boundary would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. HR and Recruiters should use the note as the base for a rejection email. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.