Review-first run
Build a lesson plan from grade level, learning objective, standard, time limit, materials, and classroom constraints, then inspect classroom evidence, grade level, learning objective, and school rules and the handoff before it reaches students, families, and school reviewers. lesson plans stays close to a classroom handoff where timing, privacy, and learner context matter, which keeps ChatGPT from drifting into generic advice.
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
Build a worksheet or practice set from topic, grade level, sample problems, answer expectations, and accommodation needs, then inspect classroom evidence, grade level, learning objective, and school rules and the handoff before it reaches students, families, and school reviewers. worksheets stays close to a classroom handoff where timing, privacy, and learner context matter, which keeps ChatGPT from drifting into generic advice.
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
A focused prompt path for teachers: gather context, create a quiz with an answer key, repair weak answers, and save only the reusable parts. quizzes needs a human pass that can replace polished filler with source-backed lines inside a quiz with an answer key before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
Teachers get a rubrics run sheet with real input, source checks, answer repair, and a handoff path for students, families, and school reviewers. rubrics gives the user a concrete criterion row with level anchors to inspect, not just wording to polish.
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 in design rubrics fails because the note should become criterion row with level anchors. The user's note should stay readable after the answer is organized. This design rubrics run should turn that note into a scoring rubric. For design rubrics, 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
A practical route from rough notes to a parent email, built around neutral family communication, requested action, meeting context, and privacy-safe wording, parent email quality, neutral family communication and requested action, and recipient-safe next step, and reusable prompt fields. parent emails gives the user a concrete message version with meeting ask and privacy-safe wording to inspect, not just wording to polish.
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 in write parent emails fails because the note should become message version with meeting ask and privacy-safe wording. A safer answer should separate source notes from guesses. This write parent emails run should turn that note into a parent email. For write parent emails, 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
A practical report card comments workflow for teachers, with variable prompts, a messy-note example, quality checks, and next-step links. report card comments treats comment bank row tied to classroom evidence as the asset to check, not as decorative output.
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 write report card comments, 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 write report card comments note into report card comments. For write report card comments, paste the source as bullets, constraints, and audience notes so the model has enough shape for report card comments formatted as clear sections, bullets, and a review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
For teachers, this page turns classroom activities into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. classroom activities needs a human pass that can replace polished filler with source-backed lines inside a classroom activity plan before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
This differentiate instruction workflow helps teachers copy the right prompt, inspect the answer, and hand off only what the source supports. differentiate instruction examples stay close to a classroom handoff where timing, privacy, and learner context matter, so the prompt has a real work setting.
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 rough study plan notes into a study plan; use the prompt, sample input, rejection rules, and review checklist together. study plan review starts at the moment where study plans can become motivational schedules without proof of gaps, exam timing, or feedback loops.
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 make a study plan 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 make a study plan, the supplied note becomes the base for a study plan. A usable make a study plan input 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 page when generate flashcards needs source notes, definitions, formulas, examples, and recall difficulty, a clear output shape, and a review pass before sharing with the student, instructor, or academic advisor. generate flashcards treats front/back card batch with recall difficulty as the asset to check, not as decorative output.
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 generate flashcards, 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 generate flashcards note into a flashcard set. For generate flashcards, paste the source as bullets, constraints, and audience notes so the model has enough shape for a flashcard set formatted as clear sections, bullets, and a review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
A focused prompt path for students: gather context, create organized lecture notes, repair weak answers, and save only the reusable parts. lecture notes needs a human pass that can replace polished filler with source-backed lines inside organized lecture notes before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
For students, this page turns essay outline into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. essay outline needs a human pass that can replace polished filler with source-backed lines inside an essay outline before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
Students get a for exams run sheet with real input, source checks, answer repair, and a handoff path for the student, instructor, or academic advisor. for exams gives the user a concrete practice plan with topic confidence bands to inspect, not just wording to polish.
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 in prepare for exams fails because the note should become practice plan with topic confidence bands. The user's note should stay readable after the answer is organized. This prepare for exams run should turn that note into an exam prep plan. For prepare for exams, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and decision 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
A focused prompt path for students: gather context, create a research paper plan, repair weak answers, and save only the reusable parts. research paper needs a human pass that can replace polished filler with source-backed lines inside a research paper plan before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
Use this internship outreach emails page to turn target company, role, connection point, experience proof, and requested next step into an internship outreach email with examples, rejection rules, and a human review pass. internship outreach emails review starts at the moment where internship email for students can sound useful while hiding the missing detail a reviewer needs.
Turn target company, role, connection point, experience proof, 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 write internship emails help only when they keep the source note visible while shaping outreach email with proof line and ask. The working prompt should keep this as the factual base. In write internship emails, the supplied note becomes the base for an internship outreach email. A usable write internship emails input 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
A active recall page for people who need an active recall practice set, not loose advice: source prep, examples, prompts, and review steps. active recall stays close to a study workflow where the user needs practice, not a finished answer to submit blindly, which keeps ChatGPT from drifting into generic advice.
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 rough resume bullets notes into resume bullets; use the prompt, sample input, rejection rules, and review checklist together. resume bullets review starts at the moment where a bullet can sound stronger by implying a metric the candidate cannot defend.
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 rewrite resume bullets 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 rewrite resume bullets, the supplied note becomes the base for resume bullets. A usable rewrite resume bullets input 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
Build a cover letter from target role, company reason, relevant proof, career story, and tone preference, then inspect true experience, measurable proof, and target role fit and the handoff before it reaches a recruiter, hiring manager, or networking contact. cover letters stays close to a hiring workflow where claims must survive recruiter or interviewer follow-up, which keeps ChatGPT from drifting into generic advice.
Turn target role, company reason, relevant proof, 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
Use this LinkedIn summaries page to turn target audience, career themes, proof points, keywords, and voice into a LinkedIn summary with examples, rejection rules, and a human review pass. LinkedIn summaries review starts at the moment where linkedin summary for job seekers can sound useful while hiding the missing detail a reviewer needs.
Turn target audience, career themes, proof points, 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 improve linkedin summaries help only when they keep the source note visible while shaping profile summary with proof and keyword lines. The working prompt should keep this as the factual base. In improve linkedin summaries, the supplied note becomes the base for a LinkedIn summary. A usable improve linkedin summaries input 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
A real-use interview answers page with a field note, runnable prompts, repair instructions, and checks for true experience, measurable proof, and target role fit. interview answers review starts at the moment where interview prep can turn into memorized lines without evidence, concern handling, or follow-up notes.
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 prepare interview answers help only when they keep the source note visible while shaping answer bank with risk and proof notes. A careful pass should keep the user's limit visible. In prepare interview answers, the supplied note becomes the base for interview answer practice. A usable prepare interview answers input 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
A copy-ready star stories workflow that starts with situation, task, action, result, lesson learned, and target competency, produces STAR interview stories formatted as clear sections, bullets, and a review checklist, and flags what humans must verify. star stories examples stay close to a hiring workflow where claims must survive recruiter or interviewer follow-up, so the prompt has a real work setting.
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 proof, and target role fit or treats uncertainty as fact.
Ready-to-run path
For job seekers, this page turns salary negotiation into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. salary negotiation needs a human pass that can replace polished filler with source-backed lines inside a salary negotiation plan before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
For job seekers, this page turns follow-up emails into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. follow-up emails needs a human pass that can replace polished filler with source-backed lines inside a follow-up email before the answer is reused.
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 proof, 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 formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. career change catches the failure point where career change for job seekers can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.
Turn past experience, new target role, transferable proof, 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 proof points. Reviewer approval for explain a career change has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start explain a career change from the rough request before shaping a career-change explanation. A usable explain a career change input 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
A real-use campaign briefs page with a field note, runnable prompts, repair instructions, and checks for source notes, examples, constraints, and reviewer judgment. campaign briefs review starts at the moment where campaign briefs can invent audience insight, proof, or channel fit beyond the notes.
Turn offer, audience, channel, proof, 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, proof is customer quote and benchmark report, channels are email, LinkedIn, and retargeting. Examples for write campaign briefs help only when they keep the source note visible while shaping brief table with offer, audience, proof, and channel. The response should not turn the case into broad advice. In write campaign briefs, the supplied note becomes the base for a campaign brief. A usable write campaign briefs input 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 ad copy page to turn product promise, audience pain, proof, channel limits, and compliance constraints into ad copy options with examples, rejection rules, and a human review pass. ad copy review starts at the moment where ad copy can add urgency or claims before the offer, evidence, and compliance boundary are checked.
Turn product promise, audience pain, proof, 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 create ad copy help only when they keep the source note visible while shaping claim-to-proof copy matrix. The first pass should name the source details it is using. In create ad copy, the supplied note becomes the base for ad copy options. A usable create ad copy input 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, proof blocks, and call to action and surface source notes, examples, constraints, and reviewer judgment. landing page copy treats page section version with objection notes as the asset to check, not as decorative output.
Turn offer, visitor intent, proof, 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, proof, FAQ, CTA. Tone calm and direct. Avoid promising tax advice. In write landing page copy, 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 write landing page copy note into landing page copy. For write landing page copy, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
For marketers, this page turns email sequences into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. email sequences needs a human pass that can replace polished filler with source-backed lines inside an email sequence before the answer is reused.
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, proof, 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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
Use this page when describe customer personas needs research notes, behaviors, pains, buying triggers, objections, and language, a clear output shape, and a review pass before sharing with a campaign owner, creative reviewer, or channel manager. describe customer personas treats persona card backed by research quotes as the asset to check, not as decorative output.
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 describe customer personas, 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 describe customer personas note into a customer persona. For describe customer personas, 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 prompts for content calendars that include source context, example inputs, answer grading, and a safe-use review lane. content calendars should only be saved after someone can replace polished filler with source-backed lines inside a content calendar.
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 proof 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 build content calendars 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
A practical competitor analysis workflow for marketers, with variable prompts, a messy-note example, quality checks, and next-step links. competitor analysis treats competitor comparison grid with evidence gaps as the asset to check, not as decorative output.
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, proof type, missing claims, pricing cue, and how our angle could differ. In structure competitor analysis, 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 structure competitor analysis note into a competitor analysis. For structure competitor analysis, 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
A practical route from rough notes to a positioning statement, built around category choice, alternative options, differentiated proof, and promise clarity, positioning statement quality, category choice and alternative options, and channel-fit proof, and reusable prompt fields. positioning gives the user a concrete positioning statement with alternative and proof to inspect, not just wording to polish.
Turn target customer, alternative options, differentiated proof, 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 proof, tagline directions, and risks for each angle. Phrase shopping in refine positioning fails because the note should become positioning statement with alternative and proof. A safer answer should separate source notes from guesses. This refine positioning run should turn that note into a positioning statement. For refine positioning, paste the source as bullets, constraints, and audience notes so the model has enough shape for a positioning statement formatted as clear sections, bullets, and a 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
A prompt set for keyword research that keeps a keyword cluster plan, intent clusters, source data caveats, page mapping, and priority scoring, and the final human check tied to the same source note. keyword research stays close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, which keeps ChatGPT from drifting into generic advice.
Turn seed keywords, Search Console 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 briefs request to a content brief formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. content briefs catches the failure point where the brief can look complete while missing the SERP angle, internal-link target, or claim boundary, because that is where polished answers usually fail.
Turn main search question, SERP 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. Reviewer approval for build content briefs has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start build content briefs from the rough request before shaping a content brief. A usable build content briefs input 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
A practical title tags workflow for seo specialists, with variable prompts, a messy-note example, quality checks, and next-step links. title tags treats title option table with intent notes as the asset to check, not as decorative output.
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 write title tags, 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 write title tags note into title tag options. For write title tags, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
A copy-ready meta descriptions workflow that starts with page value, main search question, call to action, intent, and length constraint, produces copy options grouped by angle, audience, proof point, and revision note, and flags what humans must verify. meta descriptions examples stay close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, so the prompt has a real work setting.
Turn page value, main search question, 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 links run with the working case, then copy prompts that preserve target URL priority, anchor context, crawl depth, and topical bridge and surface real search data, visible page content, and query intent. internal links treats source-target link map with anchor rationale as the asset to check, not as decorative output.
Turn site sections, target URLs, 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 plan internal links, 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 plan internal links note into an internal linking plan. For plan internal links, paste the source as bullets, constraints, and audience notes so the model has enough shape for an internal linking plan formatted as clear sections, bullets, and a review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
A refresh existing content page for people who need a content refresh brief, not loose advice: source prep, examples, prompts, and review steps. refresh existing content stays close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, which keeps ChatGPT from drifting into generic advice.
Turn current page copy, performance data, SERP 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 decision 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
A prompt workbench for analyze serp intent, covering ranking URLs, result types, query modifiers, user intent clues, and content gaps, a structured analysis table with claims, evidence, gaps, and recommended next step, review checks, and follow-up fixes. analyze serp intent examples stay close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, so the prompt has a real work setting.
Turn ranking URLs, result types, query modifiers, user intent clues, and content gaps into a SERP intent analysis for a search user, editor, or SEO lead.
- Bring first
- Need result type summary, recurring sections, PAA themes, missing proof, local intent clues, and content risks. No volume or rank claims. SERP 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 SERP 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 page when schema markup needs page type, visible content, entity details, required properties, and validation target, a clear output shape, and a review pass before sharing with a search user, editor, or SEO lead. schema markup treats schema property checklist tied to visible content as the asset to check, not as decorative output.
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 outline schema markup, 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 outline schema markup note into a schema markup plan. For outline schema markup, paste the source as bullets, constraints, and audience notes so the model has enough shape for a schema markup plan formatted as clear sections, bullets, and a review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Review-first run
A role-specific page for cold emails with a recommended prompt, filled scenario, output grader, repair prompt, and related workflows. cold emails catches the failure point where outreach can look personalized while relying on a guessed trigger, because that is where polished answers usually fail.
Turn account trigger, prospect role, pain hypothesis, proof, 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. Reviewer approval for write cold emails has to compare the first answer with the supplied note. A practical prompt should keep the missing details visible. Start write cold emails from the rough request before shaping a cold email. A usable write cold emails input 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
Build a LinkedIn outreach message from profile context, shared relevance, reason for contact, and low-friction ask, then inspect true experience, measurable proof, and target role fit and the handoff before it reaches a prospect, buyer committee, or sales manager. LinkedIn outreach stays close to a revenue workflow where buyer context and next commitment matter more than polish, which keeps ChatGPT from drifting into generic advice.
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 proof 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
A working prompt pack for sales reps who need discovery questions backed by real notes, clear limits, and reviewable output. discovery questions should only be saved after someone can replace polished filler with source-backed lines inside discovery questions.
Turn buyer role, suspected pain, account trigger, deal stage, product fit, decision path, 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 prepare discovery questions 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 formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. objections catches the failure point where objection replies can argue too early instead of separating empathy, proof, and next ask, because that is where polished answers usually fail.
Turn objection wording, buyer context, proof, 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, proof points to request, and when to pause the deal. Reviewer approval for handle objections has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start handle objections from the rough request before shaping an objection-handling response. A usable handle objections input 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
This follow-up emails workflow helps sales reps copy the right prompt, inspect the answer, and hand off only what the source supports. follow-up emails examples stay close to a revenue workflow where buyer context and next commitment matter more than polish, so the prompt has a real work setting.
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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Ready-to-run path
Use the account research workbench to move from company page, recent signals, role map, pain hypothesis, and source links to a structured analysis table with claims, evidence, gaps, and recommended next step with assumptions and reviewer checks exposed. account research catches the failure point where account research for sales can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.
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. Reviewer approval for summarize account research has to compare the first answer with the supplied note. The output should carry the user's limits into every section. Start summarize account research from the rough request before shaping an account research summary. A usable summarize account research input 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 summaries request to a call summary formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. call summaries catches the failure point where call summaries can hide owners, dates, objections, or next-step commitments, because that is where polished answers usually fail.
Turn call notes, decisions, 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. Reviewer approval for write call summaries has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start write call summaries from the rough request before shaping a call summary. A usable write call summaries input 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
A working prompt pack for sales reps who need a proposal outline backed by real notes, clear limits, and reviewable output. proposals should only be saved after someone can replace polished filler with source-backed lines inside a proposal outline.
Turn buyer problem, decision criteria, deal stage, proof, scope, assumptions, pricing context, and next-step owner into a proposal outline for a prospect, buyer committee, or sales manager.
- Bring first
- Need proposal outline, executive summary, scope, timeline, proof, 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 write proposals 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
Real Estate Agents get a listing descriptions run sheet with real input, source checks, answer repair, and a handoff path for a buyer, seller, lead, or broker reviewer. listing descriptions gives the user a concrete listing copy map with fact-only feature notes to inspect, not just wording to polish.
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 in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, 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
A copy-ready buyer emails workflow that starts with buyer criteria, listings discussed, timing, next step, and local constraints, produces a ready-to-edit message with subject line, body, tone notes, and review checklist, and flags what humans must verify. buyer emails examples stay close to a client-facing property workflow with compliance and local-fact limits, so the prompt has a real work setting.
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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Ready-to-run path
A role-specific page for seller scripts with a recommended prompt, filled scenario, output grader, repair prompt, and related workflows. seller scripts catches the failure point where seller scripts can sound confident while market evidence and legal-sensitive boundaries are thin, because that is where polished answers usually fail.
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. Reviewer approval for write seller scripts has to compare the first answer with the supplied note. A practical prompt should keep the missing details visible. Start write seller scripts from the rough request before shaping a seller script. A usable write seller scripts input 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 rough follow up after open houses notes into open house follow-up messages; use the prompt, sample input, rejection rules, and review checklist together. follow up after open houses review starts at the moment where visitor follow-up can imply interest, private facts, or next-step readiness that the notes do not prove.
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 follow up after open houses 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 follow up after open houses, the supplied note becomes the base for open house follow-up messages. A usable follow up after open houses input 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
A practical route from rough notes to a neighborhood guide outline, built around amenity categories, commute context, lifestyle fit, and source caveats, neighborhood guide outline quality, amenity categories and commute context, and local-compliance restraint, and reusable prompt fields. neighborhood guides gives the user a concrete guide outline with source-limited local notes to inspect, not just wording to polish.
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 in outline neighborhood guides fails because the note should become guide outline with source-limited local notes. The prompt should turn the note into checkable material. This outline neighborhood guides run should turn that note into a neighborhood guide outline. For outline neighborhood guides, paste the source as bullets, constraints, and audience notes so the model has enough shape for a neighborhood guide outline formatted as clear sections, bullets, and a 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
A copy-ready market updates workflow that starts with local data source, timeframe, inventory, price trend, and caveats, produces a market update formatted as clear sections, bullets, and a review checklist, and flags what humans must verify. market updates examples stay close to a client-facing property workflow with compliance and local-fact limits, so the prompt has a real work setting.
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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Review-first run
Move from a rough social posts request to copy options grouped by angle, audience, proof point, and revision note, using runnable prompts plus reject-if and repair rules. social posts catches the failure point where social posts for real estate agents can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.
Turn listing or service angle, platform, audience, proof, 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. Reviewer approval for create social posts has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start create social posts from the rough request before shaping social posts. A usable create social posts input 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
Prepare a review reply with prompts that name the source, protect the risky claims, and leave a checklist for review reply quality, public reputation and property-service context, and recipient-safe next step. reviews gives the user a concrete reply version with escalation and public-tone limits to inspect, not just wording to polish.
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 in reply to reviews fails because the note should become reply version with escalation and public-tone limits. A stronger run should protect the user's real limits. This reply to reviews run should turn that note into a review reply. For reply to reviews, 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
A prompt set for business plans that keeps a business plan outline, customer, offer, revenue logic, cost assumptions, and milestone risk, and the final human check tied to the same source note. business plans stays close to a customer-facing workflow where service boundaries and trust matter, which keeps ChatGPT from drifting into generic advice.
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
A focused prompt path for small business owners: gather context, create a local marketing plan, repair weak answers, and save only the reusable parts. local marketing needs a human pass that can replace polished filler with source-backed lines inside a local marketing plan before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
This customer service replies workflow helps small business owners copy the right prompt, inspect the answer, and hand off only what the source supports. customer service replies examples stay close to a customer-facing workflow where service boundaries and trust matter, so the prompt has a real work setting.
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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Review-first run
For small business owners, this page turns sops into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. sops needs a human pass that can replace polished filler with source-backed lines inside a standard operating procedure before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
Build a hiring post from role scope, required skills, schedule, compensation range, culture notes, and screening rules, then inspect source notes, examples, constraints, and reviewer judgment and the handoff before it reaches a customer, employee, applicant, or local buyer. hiring posts stays close to a customer-facing workflow where service boundaries and trust matter, which keeps ChatGPT from drifting into generic advice.
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
A practical reviews workflow for small business owners, with variable prompts, a messy-note example, quality checks, and next-step links. reviews treats reply version with escalation and public-tone limits as the asset to check, not as decorative output.
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 reply to reviews, 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 reply to reviews note into a review reply. For reply to reviews, 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
A working prompt pack for small business owners who need pricing page copy backed by real notes, clear limits, and reviewable output. pricing pages should only be saved after someone can replace polished filler with source-backed lines inside pricing page copy.
Turn offer tiers, customer segment, proof, 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 write pricing pages 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
Small Business Owners can start email newsletters from real notes, copy a ready prompt, and check email newsletter quality, audience segment and editorial hook, and recipient-safe next step before using the result. email newsletters needs a human pass that can replace polished filler with source-backed lines inside an email newsletter before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
A prompt workbench for proposals, covering client brief, project goal, deliverables, timeline, proof, assumptions, price context, exclusions, and approval owner, a proposal outline formatted as clear sections, bullets, and a review checklist, review checks, and follow-up fixes. proposals examples stay close to a client-service workflow where scope and approval details protect both sides, so the prompt has a real work setting.
Turn client brief, project goal, deliverables, timeline, proof, assumptions, price context, exclusions, and approval owner 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 client brief, scope boundary, approval owner, proof, exclusions, and acceptance terms or treats uncertainty as fact.
Ready-to-run path
A prompt workbench for discovery questions, covering client goal, project type, current problem, budget range, timeline, decision owner, scope risks, and approval process, discovery questions formatted as clear sections, bullets, and a review checklist, review checks, and follow-up fixes. discovery questions examples stay close to a client-service workflow where scope and approval details protect both sides, so the prompt has a real work setting.
Turn client goal, project type, current problem, budget range, timeline, decision owner, scope risks, and approval process into discovery questions for a client, prospect, or project stakeholder.
- Bring first
- Need questions about audience, offer, current page, proof, 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 proof, and target role fit or treats uncertainty as fact.
Ready-to-run path
Build a scope of work from client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules, then inspect deliverables, exclusions, revision limits, acceptance criteria, and change-request rules and the handoff before it reaches a client, prospect, or project stakeholder. scopes of work stays close to a client agreement version where unclear wording becomes scope creep, which keeps ChatGPT from drifting into generic advice.
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
Freelancers get a client onboarding run sheet with real input, source checks, answer repair, and a handoff path for a client, prospect, or project stakeholder. client onboarding gives the user a concrete onboarding checklist with owner and access fields to inspect, not just wording to polish.
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 in plan client onboarding fails 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 plan client onboarding run should turn that note into a client onboarding plan. For plan client onboarding, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and decision 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
A practical route from rough notes to a project update, built around completed work, blocker, decision needed, timeline risk, and owner, project update quality, completed work and blocker, and client-approval boundary, and reusable prompt fields. project updates gives the user a concrete status update with blocker and decision rows to inspect, not just wording to polish.
Turn completed work, blockers, decisions 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, decision needed, next milestone, timeline impact, and friendly tone. Phrase shopping in send project updates fails because the note should become status update with blocker and decision rows. A safer answer should separate source notes from guesses. This send project updates run should turn that note into a project update. For send project updates, paste the source as bullets, constraints, and audience notes so the model has enough shape for a project update formatted as clear sections, bullets, and a 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
Freelancers can start case studies from real notes, copy a ready prompt, and check case study outline quality, before state and intervention, and learning-integrity check before using the result. case studies needs a human pass that can replace polished filler with source-backed lines inside a case study outline before the answer is reused.
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 proof, 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 decision. 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 proof, numbers, or authority that the user did not provide.
Review-first run
Prepare a testimonial request with prompts that name the source, protect the risky claims, and leave a checklist for testimonial request quality, relationship context and result prompt, and client-approval boundary. request testimonials gives the user a concrete request note with approval and quote boundary to inspect, not just wording to polish.
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 in request testimonials fails because the note should become request note with approval and quote boundary. The workbench should turn this note into checkable fields. This request testimonials run should turn that note into a testimonial request. For request testimonials, paste the source as bullets, constraints, and audience notes so the model has enough shape for a testimonial request formatted as clear sections, bullets, and a 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
A prompt set for pricing that keeps a pricing explanation, cost drivers, value logic, tradeoffs, and scope protection, and the final human check tied to the same source note. pricing stays close to a client-service workflow where scope and approval details protect both sides, which keeps ChatGPT from drifting into generic advice.
Turn service scope, value proof, 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
A practical debug an issue workflow for developers, with variable prompts, a messy-note example, quality checks, and next-step links. debug an issue treats debug log with reproduction and hypothesis rows as the asset to check, not as decorative output.
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 debug an issue, 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 debug an issue note into a debugging plan. For debug an issue, 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 rough review code notes into a code review checklist; use the prompt, sample input, rejection rules, and review checklist together. review code review starts at the moment where code reviews can stay broad instead of naming file-level risks and test questions.
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 review code 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 review code, the supplied note becomes the base for a code review checklist. A usable review code input 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
Developers get a unit tests run sheet with real input, source checks, answer repair, and a handoff path for a code reviewer, teammate, maintainer, or future self. unit tests gives the user a concrete test case table with edge conditions to inspect, not just wording to polish.
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 in write unit tests fails because the note should become test case table with edge conditions. The user's note should stay readable after the answer is organized. This write unit tests run should turn that note into unit test cases. For write unit tests, 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 rough documentation notes into developer documentation; use the prompt, sample input, rejection rules, and review checklist together. documentation review starts at the moment where documentation can describe the happy path while examples and limitations stay thin.
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 write documentation 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 write documentation, the supplied note becomes the base for developer documentation. A usable write documentation input 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 page when refactoring needs current code shape, pain points, behavior to preserve, tests, and migration risk, a clear output shape, and a review pass before sharing with a code reviewer, teammate, maintainer, or future self. refactoring treats refactor plan with behavior-preservation checks as the asset to check, not as decorative output.
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 plan refactoring, 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 plan refactoring note into a refactoring plan. For plan refactoring, 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
A focused prompt path for developers: gather context, create an API integration plan, repair weak answers, and save only the reusable parts. api integration needs a human pass that can replace polished filler with source-backed lines inside an API integration plan before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Review-first run
A focused prompt path for developers: gather context, create a plain-language regex explanation, repair weak answers, and save only the reusable parts. regex needs a human pass that can replace polished filler with source-backed lines inside a plain-language regex explanation before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
A prompt workbench for learning roadmaps, covering current skill level, target outcome, time budget, projects, and feedback loop, a sequenced plan with stages, owners, timing, and decision checkpoints, review checks, and follow-up fixes. learning roadmaps examples stay close to an engineering workflow where context, tests, and reproducibility matter, so the prompt has a real work setting.
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
This prds workflow helps product managers copy the right prompt, inspect the answer, and hand off only what the source supports. prds examples stay close to a planning document where a weak assumption can become roadmap work, so the prompt has a real work setting.
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 decision 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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Ready-to-run path
Product Managers get a user stories run sheet with real input, source checks, answer repair, and a handoff path for a product team, stakeholder, customer researcher, or release owner. user stories gives the user a concrete story set with acceptance signals to inspect, not just wording to polish.
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 in write user stories fails because the note should become story set with acceptance signals. The next version should keep that rough note visible. This write user stories run should turn that note into user stories. For write user stories, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories formatted as clear sections, bullets, and a 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
Turn rough acceptance criteria notes into acceptance criteria; use the prompt, sample input, rejection rules, and review checklist together. acceptance criteria review starts at the moment where acceptance criteria can sound testable while states and edge cases are still missing.
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 define acceptance criteria 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 define acceptance criteria, the supplied note becomes the base for acceptance criteria. A usable define acceptance criteria input 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
Product Managers can start prioritize roadmaps from real notes, copy a ready prompt, and check roadmap prioritization table quality, evidence strength and effort, and decision-ready evidence before using the result. prioritize roadmaps needs a human pass that can replace polished filler with source-backed lines inside a roadmap prioritization table before the answer is reused.
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 proof, numbers, or authority that the user did not provide.
Ready-to-run path
A real-use competitor analysis page with a field note, runnable prompts, repair instructions, and checks for source notes, examples, constraints, and reviewer judgment. competitor analysis review starts at the moment where competitor notes can blur observed facts and interpretation into one confident table.
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 structure competitor analysis 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 structure competitor analysis, the supplied note becomes the base for a competitor analysis. A usable structure competitor analysis input 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
A real-use release notes page with a field note, runnable prompts, repair instructions, and checks for source notes, examples, constraints, and reviewer judgment. release notes review starts at the moment where release notes can promise value beyond shipped behavior or setup reality.
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 write release notes 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 write release notes, the supplied note becomes the base for release notes. A usable write release notes input 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
For product managers handling synthesize feedback, this page keeps the source notes, audience, output shape, and reviewer visible in one run. synthesize feedback should only be saved after someone can replace polished filler with source-backed lines inside a feedback synthesis.
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 synthesize feedback 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
A real-use customer interviews page with a field note, runnable prompts, repair instructions, and checks for true experience, measurable proof, and target role fit. customer interviews review starts at the moment where interview guides can lead the participant instead of testing assumptions neutrally.
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 plan customer interviews 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 plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input 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
A job descriptions page for people who need a job description, not loose advice: source prep, examples, prompts, and review steps. job descriptions stays close to a public role post where vague wording can create screening risk, which keeps ChatGPT from drifting into generic advice.
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 formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. interview questions catches the failure point where interview questions can lose job relevance or fairness boundaries, because that is where polished answers usually fail.
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. Reviewer approval for prepare interview questions has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start prepare interview questions from the rough request before shaping interview questions. A usable prepare interview questions input 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 prompts for interview scorecards that include source context, example inputs, answer grading, and a safe-use review lane. interview scorecards should only be saved after someone can replace polished filler with source-backed lines inside a product scorecard.
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 build interview scorecards 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 page when onboarding needs new hire role, first-week goals, tools, meetings, and success signals, a clear output shape, and a review pass before sharing with a candidate, employee, hiring panel, or HR reviewer. onboarding treats first-week plan with owner and success signal as the asset to check, not as decorative output.
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 plan onboarding, 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 plan onboarding note into an onboarding plan. For plan onboarding, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and decision 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 surveys run with the working case, then copy prompts that preserve question neutrality, anonymity, scale wording, and actionability and surface source notes, examples, constraints, and reviewer judgment. employee surveys treats survey version with anonymity and scale notes as the asset to check, not as decorative output.
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 write employee surveys, 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 write employee surveys note into an employee survey. For write employee surveys, paste the source as bullets, constraints, and audience notes so the model has enough shape for an employee survey formatted as clear sections, bullets, and a review checklist.
- Reject if
- Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Ready-to-run path
Use this performance review page to turn role expectations, examples, growth areas, goals, and HR policy into performance review prompts with examples, rejection rules, and a human review pass. performance review review starts at the moment where performance reviews can slide from observable work into personality judgment.
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 write performance review prompts 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 write performance review prompts, the supplied note becomes the base for performance review prompts. A usable write performance review prompts input 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
For hr and recruiters handling policy language, this page keeps the source notes, audience, output shape, and reviewer visible in one run. policy language should only be saved after someone can flag legal-review lines and simplify wording without changing the policy intent.
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 write policy language 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
This rejection emails workflow helps hr and recruiters copy the right prompt, inspect the answer, and hand off only what the source supports. rejection emails examples stay close to a people-operations workflow where consistency, fairness, and review ownership matter, so the prompt has a real work setting.
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 source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.