Define Acceptance Criteria: start from feature goal and edge cases

Start the acceptance criteria run from "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", then decide whether the first answer is strong enough to become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Start with the right jobUse this workflow when your note, output, and switch point line up.

First move: The first acceptance criteria run should preserve the messy input, ask for missing support, and keep given-when-then states, edge cases, and testable completion as the organizing constraint the reviewer can challenge.
Keep after run: The reusable acceptance criteria version should save the structure, not the private case details, so the next run still asks for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence instead of copying hidden assumptions.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for Product Managers if the user cannot supply feature goal, edge cases, roles, data states, and failure behavior, if the desired result is not acceptance criteria, or if given-when-then states, edge cases, and testable completion is no longer the controlling choice.

First usable run

Start with the note you actually have1/3 ready

A realistic example is loaded. Try the flow once, then clear it and paste your own working notes.

Next stepFinish the run setup2 items still need context before this becomes reusable.

Current note

Paste source notesMust keepDo not allow

PrepareSource noteReal notes are loaded.
RunCopy run prompt2 checks before copy.
ReviewReview answerCurrent choice: Repair.
SaveSave reusable version0/3 save checks closed.

Keep working laterPage work stays on this device until you save it.

Try the sample firstSee one messy note become a usable define acceptance criteria run

Messy input: The acceptance criteria reviewer first sees a rough note: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." is the rough request. A teammate checking acceptance criteria should be able to see it: use acceptance criteria as the target shape, but keep given-when-then states, edge cases, and testable completion, checker ownership, and this boundary visible: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Better answer should: An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Human edit: Before saving acceptance criteria, keep the usable structure from the first pass, move unsupported polish into questions and keep supported wording inside acceptance criteria, keep sensitive details out of the reusable prompt, and write the reusable copy in a way a product team, stakeholder, customer researcher, or release owner can act on; recheck the wording against "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and preserve this final standard: the final criteria should be unambiguous enough for engineering and QA review.

Fix before reuse2 gaps before reuseCopy can start the first pass, but the answer is not reusable until these checks are closed.

Separate facts from assumptionsMark which must-keep details came from the user and which details still need a person to check them.
Name the checker and stop ruleRun the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written. must know what to reject before the answer is reused.

Real note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
What will change: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Human check: Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.

Open run previewCheck the exact prompt before copying.

Run prompt preview

Copy this after checking the notes

Task: ChatGPT Prompts for Product Managers to Define Acceptance Criteria
Who checks it: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Paste source notes:
Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.

Must keep:
Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
feature goal, edge cases, roles, data states, and failure behavior
given-when-then states, edge cases, and testable completion

Do not allow:
Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Reject it if the final shape cannot be used by a product team, stakeholder, customer researcher, or release owner.

Readiness before copy:
- Separate facts from assumptions: Mark which must-keep details came from the user and which details still need a person to check them.
- Name the checker and stop rule: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written. must know what to reject before the answer is reused.

Run prompt:
Run this evidence-aware working copy prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a scoring table with levels, observable evidence, and reviewer notes.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a working version they can inspect against the supplied notes.

Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Record to keep: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Open answer reviewUse this after ChatGPT returns the first answer.

After ChatGPT answers

Check the answer before saving it

Check against: Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses. Output shape, define acceptance criteria: the result clearly becomes acceptance criteria, not broad advice about the task.
Reject if: Evidence issue, define acceptance criteria: the answer invents or overstates the user's notes, specific examples, constraints, and reviewer judgment. Task drift, define acceptance criteria: it ignores given-when-then states, edge cases, and testable completion and moves into a neighboring workflow.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Open first answer choiceChoose accept, repair, or reject only after review.

First answer choice

Pick accept, repair, or reject before reuse

After the first define acceptance criteria answer, the product manager should choose Accept, Repair, or Reject before saving anything as acceptance criteria prompt pattern with source notes, constraints, and review checklist. The choice must compare "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." with a scoring table with levels, observable evidence, and reviewer notes, given-when-then states, edge cases, and testable completion, and the user's notes, specific examples, constraints, and reviewer judgment.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: given-when-then states, edge cases, and testable completion, the user's notes, specific examples, constraints, and reviewer judgment, the reviewer role, the source note, or the reusable fields needed for acceptance criteria prompt pattern with source notes, constraints, and review checklist.
Do next: Ask ChatGPT for a second pass that keeps the usable structure, rewrites only the weak sections, adds missing support questions, and returns acceptance criteria in a scoring table with levels, observable evidence, and reviewer notes without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and save the corrected line only after it can be traced back to "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.".

Answer choice prompt

Repair this define acceptance criteria answer instead of accepting it. Source note: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide given-when-then states, edge cases, and testable completion, turn the user's notes, specific examples, constraints, and reviewer judgment into unsupported certainty, or skip the reviewer for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence. Return a repaired a scoring table with levels, observable evidence, and reviewer notes, a list of changed lines, and one remaining question before this can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable acceptance criteria prompt pattern with source notes, constraints, and review checklist until one option has a written choice. The saved version must keep "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." as the example, turn private or one-time details into variables, and keep the risk check "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided" visible for the next run.

Open run logRecord what happened after each ChatGPT run.

Run notes

Save the answer, problem, and next try

Use this after the first answer. A reusable prompt improves when each run records what failed and what to try next.

Answer returnedProblem foundNext try

0No run notes yet
Run the prompt once, review the answer, then save the problem and next try here.

Open saved versionTurn the reviewed answer into a reusable saved version.

Saved version

Save the final answer, human edit, and variables

Save only after review. The reusable version needs the answer, the human edit, and the reuse rule in one place.

Final answerHuman editReusable variables

Save only when

The final answer passed the answer review.The human edit names what changed before reuse.Who checks it and reuse rule are saved with the asset.

Who checks it: The human owner who approves the final packet for Product Managers to Define Acceptance Criteria before it is saved, shared, or reused.
Reuse rule: Keep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.
Saved: 0/3 checks

Saved version preview

Final saved version for: ChatGPT Prompts for Product Managers to Define Acceptance Criteria
Who checks it: The human owner who approves the final packet for Product Managers to Define Acceptance Criteria before it is saved, shared, or reused.
Use or revise before saving: Repair

Save only after review:
- Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.
- Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.
- Keep the rough note, the variables that mattered, the line proving acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the accepted-use note before a product team, stakeholder, customer researcher, or release owner gets the result.
- Current answer choice: Keep the weak answer beside the repair note, mark which line failed acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and save the corrected line only after it can be traced back to "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.".

Source note used:
Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.

Final answer:
An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Human edit:
Before saving acceptance criteria, keep the usable structure from the first pass, move unsupported polish into questions and keep supported wording inside acceptance criteria, keep sensitive details out of the reusable prompt, and write the reusable copy in a way a product team, stakeholder, customer researcher, or release owner can act on; recheck the wording against "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and preserve this final standard: the final criteria should be unambiguous enough for engineering and QA review.

Reusable variables:
[source_material]: feature goal, edge cases, roles, data states, and failure behavior
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Reuse rule: Keep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.
Stop if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

First run setup

Set up the first run

Edit notes

First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Bring first: Bring the rough case note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
Switch if: The user cannot provide feature goal, edge cases, roles, data states, and failure behavior and would need ChatGPT to invent the important facts.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Choose where you areGo to runner

Go to runnerWithin five minutes, the user should have a first acceptance criteria prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence and the user's notes, specific examples, constraints, and reviewer judgment visible before sharing anything. Start with: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Go to runner

Open switch notesWhat to bring, who checks it, and when to change workflows.

Who checks it

Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Check before using

Inspect feature goal, edge cases, roles, data states, and failure behavior, the case note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", and any open support around the user's notes, specific examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

Result acceptance criteria product managers check: open the top results and record whether they solve the task, not only a prompt phrase.

Visitor question: I have feature goal, edge cases, roles, data states, and failure behavior and need acceptance criteria for a product team, stakeholder, customer researcher, or release owner; can this define acceptance criteria page turn "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." into a scoring table with levels, observable evidence, and reviewer notes without hiding given-when-then states, edge cases, and testable completion?
5-minute outcome: Within five minutes, the user should have a first acceptance criteria prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence and the user's notes, specific examples, constraints, and reviewer judgment visible before sharing anything.
Wrong page signal: This is the wrong page if the work is closer to ChatGPT Prompts for Product Managers, if given-when-then states, edge cases, and testable completion is not the controlling choice, or if the user only wants broad ideas instead of a reviewable acceptance criteria.
Why this workflow fits: Save the rough note, the accepted prompt variables, the acceptance criteria query language, and the section that shows why this acceptance criteria should stay separate from ChatGPT Prompts for Product Managers.
Reuse choice: Reuse the output only when the answer traces back to feature goal, edge cases, roles, data states, and failure behavior, respects the risk check "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided", and gives a product team, stakeholder, customer researcher, or release owner a clear accept, repair, or reject path.

Wrong page? Write user storiesUseful next step when this workflow needs a related product managers output or review pass.

Working brief

Check the job before copying

The task belongs here when the next useful action is a reviewable a scoring table with levels, observable evidence, and reviewer notes; if the user only needs ideas, a broader prompt path is safer.

Use this when: This workflow fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a scoring table with levels, observable evidence, and reviewer notes, not a longer explanation of define acceptance criteria.
Paste this kind of note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
Expected result: An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Stop before reuse if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Human check: Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
Build when: Use this when the notes are ready and the next useful output is a scoring table with levels, observable evidence, and reviewer notes, not more brainstorming.
Stop if: Stop if the answer hides missing context, blurs assumptions, or cannot trace key claims back to the notes.
Save when: Copy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Copy prompt Check answer

Fit and safety notes

Use this workflow for

Product Managers who have real notes or context and need a structured first version of acceptance criteria.
Users who want ChatGPT to ask clarifying questions before it commits to a scoring table with levels, observable evidence, and reviewer notes.
Teams that repeat acceptance criteria and need a prompt they can adapt without losing the review step.

Do not use for

Users who want ChatGPT to invent facts, credentials, numbers, or personal details.
Situations where the output needs final approval from a qualified human before it reaches a product team, stakeholder, customer researcher, or release owner.
Work that includes private data that has not been removed or summarized safely.

Wrong page?Write user storiesUseful next step when this workflow needs a related product managers output or review pass.

Editorial method Safe use About this library

Define acceptance criteria for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become acceptance criteria.

Real input: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
Target output: An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Reject if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Scenario: A PM needs criteria for sharing a prompt collection with view-only and edit access. The acceptance criteria work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. For acceptance criteria work, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.
Bring: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. feature goal, edge cases, roles, data states, and failure behavior given-when-then states, edge cases, and testable completion
Check: The final criteria should be unambiguous enough for engineering and QA review. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. Before handing off the acceptance criteria, the human should tighten tone, verify facts, and remove any claim the source material does not support. Keep a short record of what changed before reuse. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

Variable Builder

[source_material]Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.[audience]Who will read, use, approve, or act on this product manager acceptance criteria.[goal]The choice or work outcome this product manager acceptance criteria run should support.[constraints]Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.[review_lens]Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.[task_focus]The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.

Filled prompt

Copy this filled version

Run this evidence-aware working copy prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a scoring table with levels, observable evidence, and reviewer notes.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a working version they can inspect against the supplied notes.

Show the full prompt

Expected output: Expect a scoring table with levels, observable evidence, and reviewer notes that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

First run

Run this page in four moves

Concrete outputAn acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Keep after runStore the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Reject before reuseSend it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

PrepareCollect ContextUse this when the product manager source notes are still uneven or missing the detail that would shape acceptance criteria.CopyBuild The AssetUse this when the notes are ready and the next useful output is a scoring table with levels, observable evidence, and reviewer notes, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence is checked.SavePrepare HandoffUse this when the answer is close but needs to become a repeatable asset for a product manager, not a one-off chat result.

Work notes

Start from the real note, not a blank prompt

Current input: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Who checks it: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.CopyBuild The AssetExpect a scoring table with levels, observable evidence, and reviewer notes that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.GradeReview The AnswerTreat the model answer as working copy to test and tag the parts where the user's notes, specific examples, constraints, and reviewer judgment changes the choice.SavePrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Do not start if: Stop if the answer sounds polished but still cannot show the source notes behind given-when-then states, edge cases, and testable completion.
Human check: Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.

Real note check

Check the answer against your note

This works best when the answer stays tied to the note you pasted, the question people search, and the person who can review it.

Question to compare: chatgpt prompts for product managers acceptance criteria

Open reference checks

Paste into ChatGPT: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
Question to compare: chatgpt prompts for product managers acceptance criteriaResult acceptance criteria product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Reference page: NIST AI Risk Management FrameworkUsed as an external risk-management reference where acceptance criteria needs human oversight, assumptions, and review controls.
Who checks it: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.Inspect feature goal, edge cases, roles, data states, and failure behavior, the case note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", and any open support around the user's notes, specific examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Product Managers should use this page when acceptance criteria depends on source details, recipient context, and a reviewer who can check acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence. The model needs enough context to create acceptance criteria, but the page also tells the user when to stop and ask for more evidence. acceptance criteria weak spot: acceptance criteria can sound testable while states and edge cases are still missing. The page's quality bar is whether a human can inspect the result in one pass and know what to fix. Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Use the example as a calibration point, then replace it with the user's actual source material.

Real use plan for treating the prompt like a work note

0/12 checked

The define acceptance criteria run works because it does not end at a fluent answer; the user compares the output with "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", repairs weak sections, and keeps given-when-then states, edge cases, and testable completion visible before handoff.

Before copying

Start from the actual handoff: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.Add the recipient, channel, and approval owner before asking for a finished acceptance criteria.Include the rule that decides whether the answer is safe to use: The prompt must turn vague requirements into observable behavior without prescribing code.Tell the model that given-when-then states, edge cases, and testable completion is the center of the answer, then request a scoring table with levels, observable evidence, and reviewer notes.

After ChatGPT answers

Treat the model answer as working copy to test and tag the parts where the user's notes, specific examples, constraints, and reviewer judgment changes the choice.Compare each section with the notes before editing for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.Use the next prompt to repair one clear gap around given-when-then states, edge cases, and testable completion.Keep the reusable version focused on feature goal, edge cases, roles, data states, and failure behavior, acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the approval step.

Reject the answer if

Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.Reject it if the final shape cannot be used by a product team, stakeholder, customer researcher, or release owner.Reject it if the answer treats Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. as optional cleanup.Reject it when the final pass would depend on guessing what the user meant.

Choose the next move

Open the task by naming the audience, the evidence limit, and the person who will approve the answer.

Build The Asset

Use this when the notes are ready and the next useful output is a scoring table with levels, observable evidence, and reviewer notes, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for acceptance criteria with assumptions separated from source-backed details.
Bring first: Bring the task focus: given-when-then states, edge cases, and testable completion. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete acceptance criteria.
Next check: Use the run sheet's review mode before sharing anything with a product team, stakeholder, customer researcher, or release owner.

Open prompt Prepare context Check answer

Before copying

Start from the actual handoff: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
Add the recipient, channel, and approval owner before asking for a finished acceptance criteria.
Include the rule that decides whether the answer is safe to use: The prompt must turn vague requirements into observable behavior without prescribing code.

Accept only if

Treat the model answer as working copy to test and tag the parts where the user's notes, specific examples, constraints, and reviewer judgment changes the choice.
Compare each section with the notes before editing for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Use the next prompt to repair one clear gap around given-when-then states, edge cases, and testable completion.

Reject when

Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Know when the answer is ready

Use this quick check before saving the answer, rerunning the prompt, or switching to a neighboring workflow.

Ready signal

The task is complete when the user's material "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." is reshaped as acceptance criteria arranged as a working version, check questions, and next steps, keeps given-when-then states, edge cases, and testable completion visible, and gives the owner sending this to a product team, stakeholder, customer researcher, or release owner one written call on whether to accept it, repair it, or start over before sharing with a product team, stakeholder, customer researcher, or release owner.

First run action

Begin with the supplied source feature goal, edge cases, roles, data states, and failure behavior, the intended acceptance criteria, the audience, the stop rule "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided", and the support needed for the user's notes, specific examples, constraints, and reviewer judgment.

Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and the final reason the accepted version can become acceptance criteria prompt pattern with source notes, constraints, and review checklist.
Use or revise: the owner sending this to a product team, stakeholder, customer researcher, or release owner should approve the output only if it can be traced back to feature goal, edge cases, roles, data states, and failure behavior, shows what is assumed, and does not turn the user's notes, specific examples, constraints, and reviewer judgment into a confident claim without review.
What makes this page different: Compared with broad role pages, this page stands out by tying the query "chatgpt prompts for product managers acceptance criteria" to a fillable prompt, a realistic case, an answer repair path, and a no-fake-metrics support boundary instead of only listing prompt phrases.
Why this page exists: This page deserves its own workflow for the acceptance criteria query because acceptance criteria changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby product manager page would hide given-when-then states, edge cases, and testable completion and weaken the final acceptance criteria.

Second pass

Second pass before the answer becomes reusable

Source line

Editor margin source for acceptance criteria: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." It names the practical limit the reviewer has to see before approving the result.

Human check note

a second-pass owner protecting the user's notes, specific examples, constraints, and reviewer judgment reads the first ChatGPT answer beside the rough note and decides what survives. The page should feel handled by a human because the margin note says what to keep, what to cut, what to ask, and what to rewrite before reuse. The check belongs before the prompt is saved as acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access" as the visible source line for acceptance criteria

Keep this because the rough note is the only part a product manager can compare against the answer when a scoring table with levels, observable evidence, and reviewer notes starts to sound finished.

The accepted answer should repeat or clearly map back to "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." before it adds structure.

Cut

any confident claim about the user's notes, specific examples, constraints, and reviewer judgment that the pasted note does not prove

Cut it because the support around the user's notes, specific examples, constraints, and reviewer judgment is the review risk for this page, and fluent wording can make an unsupported detail look approved.

If the source note does not show the fact, the answer should move it into a needs-checking line or remove it.

Ask

the missing audience, owner, or review detail needed before a product team, stakeholder, customer researcher, or release owner uses the answer

Ask before reuse because acceptance criteria only helps a product team, stakeholder, customer researcher, or release owner when the channel, approval owner, and open support are visible.

The next run should name the missing field instead of burying it inside a polished answer.

Rewrite

the first polished paragraph so it shows given-when-then states, edge cases, and testable completion before tone improvements

Rewrite the opening because this task is about given-when-then states, edge cases, and testable completion, not a general acceptance criteria answer that could fit any role page.

A reviewer should see given-when-then states, edge cases, and testable completion in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

a second-pass owner protecting the user's notes, specific examples, constraints, and reviewer judgment leaves this margin pass because the workflow has to protect a real source note, not only offer another prompt. For product managers working on acceptance criteria, the human-feeling part is the specific tradeoff: keep "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around given-when-then states, edge cases, and testable completion. That support trail makes the page feel edited rather than assembled from repeated blocks.

Run the second pass

Run an editorial margin pass for this task. Source note: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." Output being reviewed: [paste ChatGPT answer]. Mark four choices: Keep the source-backed detail that should survive, Cut any unsupported claim about the user's notes, specific examples, constraints, and reviewer judgment, Ask the missing question that blocks a product team, stakeholder, customer researcher, or release owner from using the result, and Rewrite the section so given-when-then states, edge cases, and testable completion stays visible before polish. End with one accept, repair, or reject choice and a reuse rule for acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

CollectCollect ContextBring the rough case note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.CopyBuild The AssetExpect a scoring table with levels, observable evidence, and reviewer notes that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.CheckReview The AnswerTreat the model answer as working copy to test and tag the parts where the user's notes, specific examples, constraints, and reviewer judgment changes the choice.HandoffPrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Wrong page ifThe user cannot provide feature goal, edge cases, roles, data states, and failure behavior and would need ChatGPT to invent the important facts.

Stay hereThis workflow fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a scoring table with levels, observable evidence, and reviewer notes, not a longer explanation of define acceptance criteria. First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Switch ifWrite user storiesUseful next step when this workflow needs a related product managers output or review pass.

Stop ifThe user cannot provide feature goal, edge cases, roles, data states, and failure behavior and would need ChatGPT to invent the important facts. The desired result is not acceptance criteria or cannot be shaped as a scoring table with levels, observable evidence, and reviewer notes.

Not forUsers who want ChatGPT to invent facts, credentials, numbers, or personal details. Situations where the output needs final approval from a qualified human before it reaches a product team, stakeholder, customer researcher, or release owner.

Before you use the answer, make the call

Who checks it: Treat the owner who will hand this to a product team, stakeholder, customer researcher, or release owner as the gate for this acceptance criteria; the answer should not move forward until they can trace it to the pasted notes.
Check before using: Inspect feature goal, edge cases, roles, data states, and failure behavior, the case note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", and any open support around the user's notes, specific examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: The checkpoint makes the page do real work: it asks whether the answer can survive acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence while still reflecting "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and the actual handoff to a product team, stakeholder, customer researcher, or release owner.
Do next: The final criteria should be unambiguous enough for engineering and QA review. Then save only the repeatable fields, not the one-time case details, so the next run still asks for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Before saving for reuse: Before reusing the answer, keep any search, traffic, ranking, or popularity claim out of the final asset unless someone can point to search performance tool evidence or other real search data after publishing for "chatgpt prompts for product managers acceptance criteria" and record where it came from.

Working case file: Define Acceptance Criteria working case for Product Managers

The page should help the user slow down long enough to name the support, owner, and stop rule. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps feature goal, edge cases, roles, data states, and failure behavior, a scoring table with levels, observable evidence, and reviewer notes, and the owner sending the result to a product team, stakeholder, customer researcher, or release owner in the same run.

Rough note

A PM needs criteria for sharing a prompt collection with view-only and edit access. The rough note says: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." The desired result is acceptance criteria for a product team, stakeholder, customer researcher, or release owner.

Constraint to keep visible

The run is not ready until the owner sending the result to a product team, stakeholder, customer researcher, or release owner can compare the answer with the source note. Carry this rule into every section: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

What the user brought

The supplied case is "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", so the answer should begin from the user's actual wording and not from broad define acceptance criteria advice.

The finished acceptance criteria should point back to feature goal, edge cases, roles, data states, and failure behavior and show how given-when-then states, edge cases, and testable completion changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any support needed for the user's notes, specific examples, constraints, and reviewer judgment before it treats the result as usable.

Missing inputs belong in a needs-checking line, not inside polished wording that a product team, stakeholder, customer researcher, or release owner might treat as settled.

Who accepts the answer

the owner sending the result to a product team, stakeholder, customer researcher, or release owner should inspect acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, compare the answer with the rough note, and decide whether the output is ready, repairable, or too thin.

The page should leave a visible owner for the final check instead of implying that ChatGPT approval is enough.

What gets saved

The reusable version should keep variables for source notes, audience, reviewer, support need, stop rule, and given-when-then states, edge cases, and testable completion.

One-time details should be removed only after the accepted answer proves that a scoring table with levels, observable evidence, and reviewer notes works for this case.

Before copying

Can the user point to the exact feature goal, edge cases, roles, data states, and failure behavior ChatGPT is allowed to use?
Is given-when-then states, edge cases, and testable completion visible before the prompt asks for acceptance criteria?
Has the user named the reviewer who checks acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence?
Is there a stop rule for unsupported claims about the user's notes, specific examples, constraints, and reviewer judgment?

Checks before sharing

Compare the first answer with "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and mark any section that invents context.
Check whether the output is shaped as a scoring table with levels, observable evidence, and reviewer notes, not a general explanation.
Move uncertain claims into a needs-checking block before sharing the answer with a product team, stakeholder, customer researcher, or release owner.
Save the pattern as acceptance criteria prompt pattern with source notes, constraints, and review checklist only after private or one-time details become variables.

Run this case first

Use this case file before writing. Start from this rough note: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." Build acceptance criteria as a scoring table with levels, observable evidence, and reviewer notes. Keep given-when-then states, edge cases, and testable completion visible, separate supplied facts from assumptions, ask for missing support around the user's notes, specific examples, constraints, and reviewer judgment, name the owner sending the result to a product team, stakeholder, customer researcher, or release owner as the checker, and stop before using any claim that the source notes do not support.

The final move is to keep the structure that saves time, then remove one-time detail before reuse. The accepted version should tell a product team, stakeholder, customer researcher, or release owner what is ready, what needs checking, and which fields the next user must replace before rerunning the prompt.

Input triage before running ChatGPT

Which problem is most likely to break this define acceptance criteria run before a product team, stakeholder, customer researcher, or release owner can use it?

Selected issue

Missing context

Build context

Symptom: Define Acceptance Criteria starts from a rough note like "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." but the audience, choice, or approval point is still implied.
Ask now: What does a product team, stakeholder, customer researcher, or release owner already know, what source notes are available, and what must the final acceptance criteria decide?
Do next: Separate facts, constraints, audience, and approval owner before copying, then ask the model to preserve those labels in the answer.
Prompt move: Before writing, ask me up to four questions needed to produce a scoring table with levels, observable evidence, and reviewer notes; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind given-when-then states, edge cases, and testable completion.
Who checks it: a product team, stakeholder, customer researcher, or release owner

Build context Readiness check

Notes to save before reusing this prompt

Sort the rough note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." before running define acceptance criteria in a product choice workflow where evidence and tradeoffs need to stay visible. This note sheet tells ChatGPT what it may use, what it must label, and which part the owner sending this to a product team, stakeholder, customer researcher, or release owner checks before a product team, stakeholder, customer researcher, or release owner sees criteria list with pass/fail examples. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

Details copied from the user's case

Capture: Capture the concrete case first: A PM needs criteria for sharing a prompt collection with view-only and edit access. The note says "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and the requested asset is criteria list with pass/fail examples. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.
Keep: Keep the facts that directly affect a scoring table with levels, observable evidence, and reviewer notes, especially the audience, task focus, channel, and any details already present in feature goal, edge cases, roles, data states, and failure behavior.
Verify: Verify that every useful line in the answer can point back to the rough note or to feature goal, edge cases, roles, data states, and failure behavior.
Prompt direction: Tell ChatGPT to use only listed facts for the first pass and to put any extra idea in a needs-checking line.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner checks whether the answer still reflects acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence after the first pass.
If skipped: If this row is skipped, acceptance criteria can sound specific while drifting into generic define acceptance criteria advice.

Guesses that need a review line

Capture: List what the user did not provide but the answer may need: missing audience detail, missing support around the user's notes, specific examples, constraints, and reviewer judgment, or an approval step for a product team, stakeholder, customer researcher, or release owner.
Keep: Keep assumptions outside the usable sections until the user confirms them or chooses a safer fallback.
Verify: Check whether the answer names what is unknown before it recommends wording, order, or next steps.
Prompt direction: Ask ChatGPT to return a short assumption list before writing any final copy or checklist.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner decides which assumptions are acceptable and which ones need another user answer.
If skipped: If assumptions are hidden, the answer may pass a style check while failing the real choice about given-when-then states, edge cases, and testable completion.

Boundaries that decide readiness

Capture: Record the rule from this case: The prompt must turn vague requirements into observable behavior without prescribing code. Also include Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. and this field friction before the model writes: acceptance criteria can sound testable while states and edge cases are still missing. Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.
Keep: Keep the constraint near the requested format so it governs the whole a scoring table with levels, observable evidence, and reviewer notes, not only the final paragraph.
Verify: Check whether the answer obeys the constraint even when it would be easier to produce a smoother or broader response.
Prompt direction: Tell ChatGPT to stop and ask before continuing if the constraint conflicts with the requested output.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner checks the constraint before approving any handoff to a product team, stakeholder, customer researcher, or release owner.
If skipped: If this row is skipped, the model may produce a fluent answer that the user cannot safely use.

Sensitive context to keep out

Capture: Mark names, private identifiers, account details, student or customer records, confidential strategy, and one-time case details before they enter the prompt.
Keep: Keep summaries that preserve meaning but remove details that should not travel into a reusable prompt.
Verify: Check whether the answer repeats private or one-time information that should have stayed outside the saved version.
Prompt direction: Ask ChatGPT to replace private details with role-safe descriptions and to flag anything it cannot safely generalize.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner confirms that the final acceptance criteria can be shared in the intended channel.
If skipped: If this row is skipped, the page helps the user copy faster but may teach a bad reuse habit.

Items that should become blanks

Capture: Name the fields that should change next time: source notes, audience, output format, support needed for the user's notes, specific examples, constraints, and reviewer judgment, reviewer, and stop rule.
Keep: Keep given-when-then states, edge cases, and testable completion, acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and criteria list with pass/fail examples as required fields so the saved prompt does not collapse into a generic role prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.
Verify: Check whether the reusable version still asks for the facts that made this case work, instead of saving the finished wording alone.
Prompt direction: Tell ChatGPT to return a reusable prompt with variables and a reject-if rule after the human accepts the current answer.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner signs off only when private details are removed and the next user can fill the variables without guessing.
If skipped: If this row is skipped, the user may save polished wording instead of a repeatable acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Copy these saved notes with the prompt only after the product manager can point to the supplied facts, the uncertain parts, the hard limit, the reusable fields for given-when-then states, edge cases, and testable completion, and the place where acceptance criteria can sound testable while states and edge cases are still missing. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. Outside support for acceptance criteria with product managers: an independent resource must mention the acceptance criteria page visibly before criteria list with pass/fail examples becomes an authority claim.

Iteration loop: run the prompt as a working thread

Define Acceptance Criteria should stay unfinished until the missing support and reviewer check are complete. Start from the rough note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", then ask ChatGPT to write, question, challenge, and hand off criteria list with pass/fail examples without hiding the user's notes, specific examples, constraints, and reviewer judgment. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

Thread goal

Thread goal for product manager: turn the rough case from A PM needs criteria for sharing a prompt collection with view-only and edit access. into a scoring table with levels, observable evidence, and reviewer notes for a product team, stakeholder, customer researcher, or release owner, while the owner deciding whether this becomes acceptance criteria prompt pattern with source notes, constraints, and review checklist can still inspect acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, given-when-then states, edge cases, and testable completion, unsupported assumptions, and the friction that acceptance criteria can sound testable while states and edge cases are still missing. Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.

Define Acceptance Criteria should keep the task-specific support trail and remove one-time details before reuse. The loop is stronger than a one-shot prompt because it makes the model show its first version, missing context, challenge, and reusable handoff before the product manager treats criteria list with pass/fail examples as finished. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

1
Working pass
Use this first when the source note is messy but concrete enough to produce a reviewable acceptance criteria.
```
Define Acceptance Criteria first run: use the rough note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." from A PM needs criteria for sharing a prompt collection with view-only and edit access.; build acceptance criteria as a scoring table with levels, observable evidence, and reviewer notes; rely on supplied facts for the main answer, label assumptions, keep given-when-then states, edge cases, and testable completion visible, and end with the support still needed for the user's notes, specific examples, constraints, and reviewer judgment.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports given-when-then states, edge cases, and testable completion.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the owner deciding whether this becomes acceptance criteria prompt pattern with source notes, constraints, and review checklist something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats the user's notes, specific examples, constraints, and reviewer judgment as proven, or drifts into general define acceptance criteria advice.
2
Missing support pass
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Define Acceptance Criteria gap fill: compare the first answer with the rough note already in this thread; name the missing inputs that prevent a product team, stakeholder, customer researcher, or release owner from using the result; ask up to five questions grouped by audience, source support, channel, reviewer, and reuse field, then say which part can continue with a safe fallback.
```
Keep
Keep any section that maps to feature goal, edge cases, roles, data states, and failure behavior; move guesses into open questions instead of deleting the whole answer.
Accept if
Accept this turn only if the missing questions would help a product manager make a clearer choice before rerunning or revising.
Stop if
Stop if the model asks generic questions that do not affect a scoring table with levels, observable evidence, and reviewer notes, acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, or the final handoff.
3
Reviewer challenge
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Define Acceptance Criteria skeptic pass: compare the current answer with the rough note already in this thread; mark unsupported claims, unclear owners, privacy issues, and weak spots around the user's notes, specific examples, constraints, and reviewer judgment; give each issue a repair sentence that keeps given-when-then states, edge cases, and testable completion visible without adding new facts.
```
Keep
Keep the usable structure from the first answer, but require every claim and recommendation to survive the skeptic pass.
Accept if
Accept this turn only if it gives repair instructions that the owner deciding whether this becomes acceptance criteria prompt pattern with source notes, constraints, and review checklist can apply without rewriting the whole asset from scratch.
Stop if
Stop if the critique only says the answer is good or bad without naming the exact line, risk, and repair move.
4
Final pass
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Define Acceptance Criteria handoff: prepare the accepted acceptance criteria, a needs-checking block for the user's notes, specific examples, constraints, and reviewer judgment, a reviewer note for the owner deciding whether this becomes acceptance criteria prompt pattern with source notes, constraints, and review checklist, and a reusable version with variables for source notes, audience, output format, support need, stop rule, and given-when-then states, edge cases, and testable completion; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair choices, and the variables that make acceptance criteria prompt pattern with source notes, constraints, and review checklist safe to rerun.
Accept if
Accept the handoff only if a product team, stakeholder, customer researcher, or release owner can tell what is ready, what needs review, and what must be replaced next time.
Stop if
Stop if the final version saves polished case details instead of a reusable prompt structure with visible boundaries.

Prompt readiness check before you copy

Use this quick pass to decide whether to collect more context, build a context pack, or run the prompt and grade the answer.

0/6 ready

Source notes readyNeed Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.Audience or recipient knownProduct Managers who have real notes or context and need a structured first version of acceptance criteria.Constraints and no-go rules clearPrompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Ask ChatGPT to label assumptions and verification needs before using acceptance criteria.Facts to verify listedAcceptance Criteria output shape: what would make a scoring table with levels, observable evidence, and reviewer notes easier to review in one pass? Acceptance Criteria choice detail: which rough-note detail changes the choice for a product team, stakeholder, customer researcher, or release owner?Checker is namedRun the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.Reuse rule clearKeep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

Do next

Collect context first

The prompt can run, but the answer will likely fill gaps with assumptions. Start by collecting notes, constraints, and the person who will check it.

Use this prompt when: Product Managers who have real notes or context and need a structured first version of acceptance criteria.
Wait if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Who checks it: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.
Reuse rule: Keep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

Collect context Open prompt Context pack Output grader

Session handoff: finish the run without losing the thread

Track the four steps that turn a copied prompt into a usable work session.

0/4 steps

Context readyBuild a context pack before copying anything.Open stepPrompt runRun the recommended prompt with the prepared context.Open stepAnswer checkedGrade the answer against the task checks and repair weak sections.Open stepReuse choiceDecide whether to save the run, rerun it, or discard it.Open step

Next action

Collect working context

Start by getting source notes, constraints, the person who checks it, and the stop rule into one place.

Working note: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.
Who checks it: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.
Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Reuse choice: Keep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

Open next step Prompt Context Grade

Work note: what the rough note changes

Use this when the answer must carry the original note, the missing context, and the review check into the final prompt run.

Original working note

The acceptance criteria reviewer first sees a rough note: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." is the rough request. A teammate checking acceptance criteria should be able to see it: use acceptance criteria as the target shape, but keep given-when-then states, edge cases, and testable completion, checker ownership, and this boundary visible: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Received note: Received note for Product Managers Define Acceptance Criteria: "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." arrives as the source note inside a product choice workflow where evidence and tradeoffs need to stay visible, with The prompt must turn vague requirements into observable behavior without prescribing code. as the first human concern and criteria list with pass/fail examples as the target artifact.
Question before run: Before writing, ask whether a scoring table with levels, observable evidence, and reviewer notes should optimize for speed, reviewability, or reuse, because the same note can lead to different define acceptance criteria outputs.
First answer flaw: First answer flaw for Product Managers Define Acceptance Criteria: the first response may hide the handoff risk by sounding complete, even though a product team, stakeholder, customer researcher, or release owner still needs support, limits, and a choice owner.
Human edit: Human edit for Product Managers Define Acceptance Criteria: separate the keeper wording from one-time facts, keep the choice path visible, and make the final version safe for the reviewer accountable for the user's notes, specific examples, constraints, and reviewer judgment to inspect; the editor also has to move unsupported polish into questions and keep supported wording inside acceptance criteria; the edit has to preserve "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and leave criteria list with pass/fail examples ready for a reviewer, not just prettier.
Reusable field: Reusable field for Product Managers Define Acceptance Criteria: keep the field set narrow: original note, final artifact, human check, unsupported items, and the reuse rule that protects prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Keep the field set alert to this repeat risk: acceptance criteria can sound testable while states and edge cases are still missing.

Questions before reuse

Acceptance Criteria output shape: what would make a scoring table with levels, observable evidence, and reviewer notes easier to review in one pass?
Acceptance Criteria choice detail: which rough-note detail changes the choice for a product team, stakeholder, customer researcher, or release owner?
Acceptance Criteria reader check: who will read or approve this acceptance criteria, and what do they already know?

Who checks it

Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Acceptance Criteria source note: treat "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." as the factual base, not decorative background; the next usable asset is criteria list with pass/fail examples.
Acceptance Criteria evidence check: mark any section where the user's notes, specific examples, constraints, and reviewer judgment is assumed instead of shown, especially when acceptance criteria can sound testable while states and edge cases are still missing.
Acceptance Criteria scope check: keep the answer on given-when-then states, edge cases, and testable completion; do not drift away from a product choice workflow where evidence and tradeoffs need to stay visible.
Acceptance Criteria final polish: rewrite final wording only after acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence is clear enough for the reviewer accountable for the user's notes, specific examples, constraints, and reviewer judgment, then move unsupported polish into questions and keep supported wording inside acceptance criteria.
Acceptance Criteria freshness rule: For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

Usable output

An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Save this noteRough note that changes the prompt: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Task-specific source material: feature goal, edge cases, roles, data states, and failure behavior Human check to keep visible: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence

Stop hereSend it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Save for reuseKeep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

Build context pack Check output Open work sample

Prompt run from pasted notes

Use this pass to see what should happen between the rough note and the answer that is safe enough to review.

Pasted notes

A rough acceptance criteria note reads: A PM needs criteria for sharing a prompt collection with view-only and edit access. The source says "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." The answer needs to become criteria list with pass/fail examples for a product team, stakeholder, customer researcher, or release owner; the run lives in a product choice workflow where evidence and tradeoffs need to stay visible and has to respect this rule before any wording polish: The prompt must turn vague requirements into observable behavior without prescribing code.

Why this input is messy

The acceptance criteria case needs intake because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over the user's notes, specific examples, constraints, and reviewer judgment, miss given-when-then states, edge cases, and testable completion, or make acceptance criteria look ready before the reviewer accountable for the user's notes, specific examples, constraints, and reviewer judgment checks it, especially when acceptance criteria can sound testable while states and edge cases are still missing.

First prompt move

Define Acceptance Criteria prompt opener should identify the choice this answer supports, then write only the sections backed by the pasted notes and flag the rest for review; this is a context pass before polish because a scoring table with levels, observable evidence, and reviewer notes has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in acceptance criteria: who will read this acceptance criteria, and what do they already know?
Source detail in acceptance criteria: which note details are verified facts, and which parts still need the user's notes, specific examples, constraints, and reviewer judgment?
Constraint detail in acceptance criteria: what tone, length, channel, or approval rule matters before the answer reaches a product team, stakeholder, customer researcher, or release owner?
Reuse detail in acceptance criteria: which person will inspect acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and what would make the answer unsafe to reuse?

Usable answer shape

The requested acceptance criteria output should return a scoring table with levels, observable evidence, and reviewer notes, separate source-backed sections from assumptions and open questions, show how given-when-then states, edge cases, and testable completion shaped the result, name the reviewer accountable for the user's notes, specific examples, constraints, and reviewer judgment, and end with a short check for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence before the answer is shared or saved.

Human revision

Before saving acceptance criteria, keep the usable structure from the first pass, move unsupported polish into questions and keep supported wording inside acceptance criteria, keep sensitive details out of the reusable prompt, and write the reusable copy in a way a product team, stakeholder, customer researcher, or release owner can act on; recheck the wording against "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and preserve this final standard: the final criteria should be unambiguous enough for engineering and QA review.

Save or discard

Reuse acceptance criteria only if the note, output shape, checker, criteria list with pass/fail examples, and reuse rule stay visible; rerun or discard the answer when it could fit another product manager task without changing the source notes, or when the user's notes, specific examples, constraints, and reviewer judgment is implied but not checkable.

Run prompt Grade answer Repair answer

Choose the right workflow for this job

Work moment

This workflow fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a scoring table with levels, observable evidence, and reviewer notes, not a longer explanation of define acceptance criteria.

Why this workflow

The task belongs here when the next useful action is a reviewable a scoring table with levels, observable evidence, and reviewer notes; if the user only needs ideas, a broader prompt path is safer.

Do first

Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Next best workflow

Write user storiesUseful next step when this workflow needs a related product managers output or review pass.

What to look for

Rough note that changes the prompt: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
Task-specific source material: feature goal, edge cases, roles, data states, and failure behavior
Human check to keep visible: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
Evidence pressure point: the user's notes, specific examples, constraints, and reviewer judgment

Wrong page if

The user cannot provide feature goal, edge cases, roles, data states, and failure behavior and would need ChatGPT to invent the important facts.
The desired result is not acceptance criteria or cannot be shaped as a scoring table with levels, observable evidence, and reviewer notes.
The task would be safer on Write user stories because the main choice is closer to that workflow.

When workflows look similar

Use this when the page looks close, but the thing you need to make or the person checking it is different.

Write PRDs: Use this workflow
Stay with ChatGPT Prompts for Product Managers to Define Acceptance Criteria when your notes already include this check: Task-specific source material: feature goal, edge cases, roles, data states, and failure behavior.; Switch instead
Switch to Write PRDs when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The user cannot provide feature goal, edge cases, roles, data states, and failure behavior and would need ChatGPT to invent the important facts.
Write user stories: Use this workflow
Stay with ChatGPT Prompts for Product Managers to Define Acceptance Criteria when your notes already include this check: Human check to keep visible: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.; Switch instead
Switch to Write user stories when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The desired result is not acceptance criteria or cannot be shaped as a scoring table with levels, observable evidence, and reviewer notes.
Prioritize roadmaps: Use this workflow
Stay with ChatGPT Prompts for Product Managers to Define Acceptance Criteria when your notes already include this check: Evidence pressure point: the user's notes, specific examples, constraints, and reviewer judgment.; Switch instead
Switch to Prioritize roadmaps when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The task would be safer on Write user stories because the main choice is closer to that workflow.

Run the page by work state

Open the task by naming the audience, the evidence limit, and the person who will approve the answer.

Build The Asset

Use this when the notes are ready and the next useful output is a scoring table with levels, observable evidence, and reviewer notes, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for acceptance criteria with assumptions separated from source-backed details.
Bring: Bring the task focus: given-when-then states, edge cases, and testable completion. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete acceptance criteria.
Next check: Use the run sheet's review mode before sharing anything with a product team, stakeholder, customer researcher, or release owner.

Bring this

Bring feature goal, edge cases, roles, data states, and failure behavior; add the reviewer, the audience, and the boundary from this case: The prompt must turn vague requirements into observable behavior without prescribing code.

Reusable handoff

The output should be easy to copy, but harder to misuse: every risky claim needs a visible check and a clear owner before reuse.

Reality checks

Does the page-specific note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." change the prompt, or could this still fit another task unchanged?
Can the reviewer check acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence without asking ChatGPT to invent missing facts?
Does the answer become acceptance criteria, or does it stay at broad acceptance criteria advice?
Would a product team, stakeholder, customer researcher, or release owner know what was provided, what was assumed, and what still needs review?

Prompt path by where the work is stuck

advanced

Define acceptance criteria for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become acceptance criteria.

Use this when: Use before asking ChatGPT for acceptance criteria so the model has enough task-specific context.
When this fits: Turn feature goal, edge cases, roles, data states, and failure behavior into acceptance criteria for a product team, stakeholder, customer researcher, or release owner.
Do next: Treat the model answer as working copy to test and tag the parts where the user's notes, specific examples, constraints, and reviewer judgment changes the choice.

Open this prompt card

Context pack before copying

0/8

Source notes are availableAudience or recipient is namedConstraints are explicitFacts to verify are listedChecker is named

Working notesConstraintsWho checks it

Ready to paste

Context brief for the next prompt

Context pack for Product Managers to Define Acceptance Criteria

Goal: Find a copyable prompt workbench that helps product managers with acceptance criteria, using the right source material, review lens, example, and follow-up prompts.
Working scenario: A PM needs criteria for sharing a prompt collection with view-only and edit access. The acceptance criteria work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. For acceptance criteria work, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.

What I know:
Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.

Constraints and no-go rules:
Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Ask ChatGPT to label assumptions and verification needs before using acceptance criteria. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Readiness checks:
- [ ] Source notes are available
- [ ] Audience or recipient is named
- [ ] Constraints are explicit
- [ ] Facts to verify are listed
- [ ] Checker is named

Ask ChatGPT to request missing context before writing. Keep assumptions separate from source-based claims.

Ask first

Questions to ask before the next run

5 questions

What source note should the answer use for Product Managers to Define Acceptance Criteria?
Who will read or use the final answer?
Which limits must stay visible, especially prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.?
Which facts should be checked before accepting the answer for ChatGPT Prompts for Product Managers to Define Acceptance Criteria?
Who should check the answer before it is reused: Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.?

Output grader before reuse

0/5

Paste ChatGPT output

0 words checked against Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.Output shape, define acceptance criteria: the result clearly becomes acceptance criteria, not broad advice about the task.Handoff clarity, define acceptance criteria: the answer names missing inputs and the next human check for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.Audience fit, define acceptance criteria: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and choice context.Risk boundary, define acceptance criteria: the final version respects Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Needs another review pass

acceptance criteria final pass: keep the useful structure, then move unsupported polish into questions and keep supported wording inside acceptance criteria; readiness means a product team, stakeholder, customer researcher, or release owner can see what was provided, what was assumed, why acceptance criteria can sound testable while states and edge cases are still missing, and what still needs review.

Task-specific output diagnosis

Paste the first Define Acceptance Criteria answer and compare it with "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." before checking style. A useful product manager output must prove it belongs to this page by keeping given-when-then states, edge cases, and testable completion, a scoring table with levels, observable evidence, and reviewer notes, and the task reviewer visible.

Pass when

The answer uses "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." as the controlling case, not as decoration, and turns it into a scoring table with levels, observable evidence, and reviewer notes with given-when-then states, edge cases, and testable completion still visible.
The answer shows which lines come from "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the acceptance criteria.
The answer gives the task reviewer a clear check tied to "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", especially the point where the user's notes, specific examples, constraints, and reviewer judgment cannot be treated as proven.
The answer can become acceptance criteria prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." are replaced with variables and the stop rule stays attached.

False pass

It sounds polished but never quotes or preserves the specific case in "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.", so the define acceptance criteria output could fit another page.
It gives a generic next step while hiding given-when-then states, edge cases, and testable completion, which makes the answer feel useful before it can support the real acceptance criteria.
It skips the task reviewer or buries the review check, so the user cannot tell who should approve the answer before reuse.
It could fit a neighboring workflow because the response hides a scoring table with levels, observable evidence, and reviewer notes, the user's notes, specific examples, constraints, and reviewer judgment, or the source material that makes this define acceptance criteria page different.

Repair next

Rewrite the opening around "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and keep the first sentence tied to given-when-then states, edge cases, and testable completion before improving tone or length.
Add a needs-checking block for the user's notes, specific examples, constraints, and reviewer judgment, then separate supplied facts from assumptions before returning a scoring table with levels, observable evidence, and reviewer notes.
Mark the line the task reviewer must inspect for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved acceptance criteria prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the define acceptance criteria check.

Red flags

Evidence issue, define acceptance criteria: the answer invents or overstates the user's notes, specific examples, constraints, and reviewer judgment.
Task drift, define acceptance criteria: it ignores given-when-then states, edge cases, and testable completion and moves into a neighboring workflow.
Readiness gap, define acceptance criteria: it sounds complete while leaving acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence impossible to verify.
Privacy issue, define acceptance criteria: it includes details that should have been summarized or removed.
Generic output, define acceptance criteria: it produces a broad template that could fit any task in the role.

Choose the next pass

Pick what happens to this answer before it becomes a saved version.

Repair

Issue note

Repair next

Run a narrower pass against the failed line, the source note, and the task-specific stop rule.

Rewrite the opening around "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and keep the first sentence tied to given-when-then states, edge cases, and testable completion before improving tone or length.
Add a needs-checking block for the user's notes, specific examples, constraints, and reviewer judgment, then separate supplied facts from assumptions before returning a scoring table with levels, observable evidence, and reviewer notes.

Repair pass

Output next pass for: Define Acceptance Criteria: start from feature goal and edge cases
Next pass: Repair
Why: Run a narrower pass against the failed line, the source note, and the task-specific stop rule.
Checked items: 0/5
Issue note: Add the failed line or remaining risk before copying this pass.

Source task:
Find a copyable prompt workbench that helps product managers with acceptance criteria, using the right source material, review lens, example, and follow-up prompts.

Repair moves:
- Rewrite the opening around "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and keep the first sentence tied to given-when-then states, edge cases, and testable completion before improving tone or length.
- Add a needs-checking block for the user's notes, specific examples, constraints, and reviewer judgment, then separate supplied facts from assumptions before returning a scoring table with levels, observable evidence, and reviewer notes.
- Mark the line the task reviewer must inspect for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, and move unsupported claims out of the usable answer.
- Replace one-time details with variables for the saved acceptance criteria prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the define acceptance criteria check.

Keep if repaired:
- The answer uses "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." as the controlling case, not as decoration, and turns it into a scoring table with levels, observable evidence, and reviewer notes with given-when-then states, edge cases, and testable completion still visible.
- The answer shows which lines come from "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the acceptance criteria.

Answer being graded:
Paste the ChatGPT answer above before copying this pass.

Return the smallest revised answer, the line a person must check, and whether this should be accepted, repaired again, or rejected.

Answer repair for replies that sound right but are not ready

Weak answer pattern

The polished Product Managers Define Acceptance Criteria version copies a line like "The notes have been shaped into a clear answer with a helpful structure, direct wording, and a closing recommendation" and then moves on. Define Acceptance Criteria failure to avoid for product manager: it makes reuse tempting even though the one-time facts have not become variables; the actual note to protect is Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.

Why it fails

Define Acceptance Criteria repair note: the response sounds helpful while sliding away from the task that the user actually brought Rebuild the weak answer around given-when-then states, edge cases, and testable completion; call out where the user's notes, specific examples, constraints, and reviewer judgment changes the answer, name the reviewer who checks the user's notes, specific examples, constraints, and reviewer judgment before sharing with a product team, stakeholder, customer researcher, or release owner, and handle the field-level problem directly: acceptance criteria can sound testable while states and edge cases are still missing.

Trace the rough note

Problem: The answer mentions acceptance criteria but does not reflect the concrete case: A PM needs criteria for sharing a prompt collection with view-only and edit access.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where criteria list with pass/fail examples changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Repair: Add a reviewer line for the reviewer who checks the user's notes, specific examples, constraints, and reviewer judgment, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply the user's notes, specific examples, constraints, and reviewer judgment even when the source notes do not support it.
Repair: Keep unsupported claims in a separate needs-checking block and remove any claim the user cannot verify.

Keep the task narrow

Problem: The response can drift from define acceptance criteria into broad advice that does not produce a scoring table with levels, observable evidence, and reviewer notes.
Repair: Force the final answer back into a scoring table with levels, observable evidence, and reviewer notes, keep given-when-then states, edge cases, and testable completion as the main choice point, and move unsupported polish into questions and keep supported wording inside acceptance criteria.

Human-edited direction

Human Define Acceptance Criteria revision for Product Managers: start with the actual case, name the audience, return a scoring table with levels, observable evidence, and reviewer notes, keep supplied notes, assumptions, and missing checks separate, then move unsupported polish into questions and keep supported wording inside acceptance criteria, tell a product team, stakeholder, customer researcher, or release owner what is ready to use, what the reviewer who checks the user's notes, specific examples, constraints, and reviewer judgment must verify, and how the answer becomes acceptance criteria prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun Product Managers Define Acceptance Criteria: repair this define acceptance criteria answer, keep the result focused on given-when-then states, edge cases, and testable completion, return a scoring table with levels, observable evidence, and reviewer notes, put unsupported claims about the user's notes, specific examples, constraints, and reviewer judgment in a needs-checking block, name the reviewer as the reviewer who checks the user's notes, specific examples, constraints, and reviewer judgment, protect this boundary "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.", and use only these source notes: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.

Accept when

The answer visibly uses the rough note instead of generic define acceptance criteria advice.
The result is shaped as a scoring table with levels, observable evidence, and reviewer notes and can be checked by the reviewer who checks the user's notes, specific examples, constraints, and reviewer judgment.
Any uncertain point about the user's notes, specific examples, constraints, and reviewer judgment is separated from the usable parts.
The reusable version keeps given-when-then states, edge cases, and testable completion and removes one-time or private details.

Reject when

The answer could fit another product manager task without changing more than the title.
The response sounds polished but cannot show where the key claims came from.
The result skips acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence or hides who should approve it.
The answer asks the user to trust the model instead of checking the source notes.

Start from the user's actual notes

Reader situation

PMs need acceptance criteria prompts that make behavior, states, and edge cases testable. This page is for product managers acceptance criteria work when acceptance criteria can sound testable while states and edge cases are still missing. Search edge for acceptance criteria with product managers: show criteria list with pass/fail examples, a human review path for acceptance criteria, and the task-specific reason the page deserves the query. Outside support for acceptance criteria with product managers: an independent resource must mention the acceptance criteria page visibly before criteria list with pass/fail examples becomes an authority claim. Acceptance criteria work for product manager needs its own page because the work here is not phrase-shopping; it is turning feature goal, edge cases, roles, data states, and failure behavior into an answer that survives acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Concrete scenario

A PM needs criteria for sharing a prompt collection with view-only and edit access. The acceptance criteria work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. For acceptance criteria work, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.

Real user input

Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Examples for acceptance criteria work help only when they keep the source note visible while shaping criteria list with pass/fail examples. The response should leave the source trail easy to inspect. In acceptance criteria work, the supplied note becomes the base for acceptance criteria. A usable starting note for acceptance criteria work includes what is known, what is uncertain, and what the reviewer must verify.

Editor take

The prompt must turn vague requirements into observable behavior without prescribing code. In this acceptance criteria review, the edit is to move unsupported polish into questions and keep supported wording inside acceptance criteria. Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch. In the acceptance criteria work review, the editorial test is whether the answer can be checked quickly against acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence and the user's actual source; compare the answer with the actual notes before reuse.

Human polish

The final criteria should be unambiguous enough for engineering and QA review. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible. Before handing off the acceptance criteria, the human should tighten tone, verify facts, and remove any claim the source material does not support. Keep a short record of what changed before reuse. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

Fast use path

Main card for acceptance criteria: use the main prompt as the first pass so the page stays action-oriented.
Source material for acceptance criteria: replace [source_material] with feature goal, edge cases, roles, data states, and failure behavior.
Audience details for acceptance criteria: fill in the audience, channel, and approval point before asking for a finished answer.
Review pass for acceptance criteria: ask for a second pass that flags issues in acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Specificity signals

A PM needs criteria for sharing a prompt collection with view-only and edit access.
Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
feature goal, edge cases, roles, data states, and failure behavior
given-when-then states, edge cases, and testable completion
the user's notes, specific examples, constraints, and reviewer judgment
Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
criteria list with pass/fail examples
acceptance criteria can sound testable while states and edge cases are still missing
move unsupported polish into questions and keep supported wording inside acceptance criteria
a product choice workflow where evidence and tradeoffs need to stay visible
For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.
Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.
Search edge for acceptance criteria with product managers: show criteria list with pass/fail examples, a human review path for acceptance criteria, and the task-specific reason the page deserves the query.
Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.
Outside support for acceptance criteria with product managers: an independent resource must mention the acceptance criteria page visibly before criteria list with pass/fail examples becomes an authority claim.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

Acceptance Criteria output shape: what would make a scoring table with levels, observable evidence, and reviewer notes easier to review in one pass?
Acceptance Criteria choice detail: which rough-note detail changes the choice for a product team, stakeholder, customer researcher, or release owner?
Acceptance Criteria reader check: who will read or approve this acceptance criteria, and what do they already know?
Acceptance Criteria stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

Acceptance Criteria source note: treat "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access." as the factual base, not decorative background; the next usable asset is criteria list with pass/fail examples.
Acceptance Criteria evidence check: mark any section where the user's notes, specific examples, constraints, and reviewer judgment is assumed instead of shown, especially when acceptance criteria can sound testable while states and edge cases are still missing.
Acceptance Criteria scope check: keep the answer on given-when-then states, edge cases, and testable completion; do not drift away from a product choice workflow where evidence and tradeoffs need to stay visible.
Acceptance Criteria final polish: rewrite final wording only after acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence is clear enough for the reviewer accountable for the user's notes, specific examples, constraints, and reviewer judgment, then move unsupported polish into questions and keep supported wording inside acceptance criteria.
Acceptance Criteria freshness rule: For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.
Acceptance Criteria failure pattern: Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.
Acceptance Criteria choice owner: Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

Before and after

Weak answer risk: The risky acceptance criteria version sounds complete: the answer sounds complete while turning "need given-when-then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access;" into broad advice, hiding missing context around the user's notes, specific examples, constraints, and reviewer judgment, and leaving a product team, stakeholder, customer researcher, or release owner without a clear choice path because acceptance criteria can sound testable while states and edge cases are still missing. Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.
Improved outcome: An acceptable acceptance criteria shape would return acceptance criteria split into reader-ready copy, open questions, and reviewer notes; make the supported lines easy to separate from assumptions and blanks, identify the person who owns the last pass and the item they inspect, prepare criteria list with pass/fail examples, and give the human reviewer a pass/fail look at acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Why it feels real: The concrete detail in acceptance criteria is the review moment: it starts from messy source notes, a product choice workflow where evidence and tradeoffs need to stay visible, a named review moment, and task-level evidence instead of a clean prompt sentence. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.

When to save this version

Keep this acceptance criteria pattern only after private details are removed, one-time facts become variables, move unsupported polish into questions and keep supported wording inside acceptance criteria, and the review rule for given-when-then states, edge cases, and testable completion still appears in the reusable prompt. Approval for product managers acceptance criteria belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the criteria list with pass/fail examples review standard visible.

The job this page helps finish

The best match is a page that lets the user run the prompt, check the answer, and repair weak sections without leaving the workflow. It should surface assumptions, open questions, and unsupported claims before the final handoff. The page is different from neighboring tasks because given-when-then states, edge cases, and testable completion changes the run.

Use Cases

Turn feature goal, edge cases, roles, data states, and failure behavior into acceptance criteria for a product team, stakeholder, customer researcher, or release owner.
Review an existing acceptance criteria answer for acceptance criteria checkpoint, missing details, and unsupported claims.
Create a repeatable acceptance criteria prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make given-when-then states, edge cases, and testable completion visible so the answer stays tied to acceptance criteria instead of drifting into a neighboring task.
Condense a long ChatGPT answer into a scoring table with levels, observable evidence, and reviewer notes without losing the choices the human must make.

Input Prep

Write the audience or recipient in one sentence, including what they already know.
Paste or summarize feature goal, edge cases, roles, data states, and failure behavior; do not ask the model to guess it.
Name the final choice the acceptance criteria output must support.
Add constraints such as tone, length, required sections, privacy limits, and forbidden claims.
List the facts that must be checked after ChatGPT answers, especially the user's notes, specific examples, constraints, and reviewer judgment.
Add the task-specific focus: given-when-then states, edge cases, and testable completion.

Check the answer against real references

What users are trying to finish

The intent is not inspiration alone; it is to move from feature goal, edge cases, roles, data states, and failure behavior to a scoring table with levels, observable evidence, and reviewer notes with evidence gaps visible. The page should earn trust by separating what the user supplied from what the model inferred. The page should feel different from a generic collection because feature goal, edge cases, roles, data states, and failure behavior drives acceptance criteria, then acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence tests the result.

Why the workflow matters

The differentiator is the acceptance path, not just the wording: users get the evidence to inspect and the rule for rejecting a plausible answer. The content stays competitive by making the output inspectable instead of relying on a longer list of prompt variations.

External references

Google Search Central people-first content guidanceUsed as the search-quality yardstick because this page must solve a real user task and make the user's notes, specific examples, constraints, and reviewer judgment reviewable.
Google Search Central SEO Starter GuideUsed to keep titles, descriptions, links, and page structure focused on helping search engines and users understand acceptance criteria.
OpenAI ChatGPT business overviewUsed for work-related prompt boundaries where AI output should support productivity while staying subject to human review.
NIST AI Risk Management FrameworkUsed as an external risk-management reference where acceptance criteria needs human oversight, assumptions, and review controls.
FTC advertising and marketing guidanceUsed as the second product reference when acceptance criteria affects market-facing claims, support language, or customer communication.

Related ways people ask for this task

Question covered: chatgpt prompts for product managers acceptance criteria

What the reader wants: copy prompt workflow with template and review intent

Leave out popularity or ranking numbers until you can point to real search data after publishing.

Related ways people ask for this task

acceptance criteria chatgpt prompt for product managers
best chatgpt prompts for acceptance criteria
acceptance criteria prompt template for product managers
copyable acceptance criteria chatgpt prompt
acceptance criteria ai prompt with review checklist
chatgpt acceptance criteria workflow prompt

What to compare before using this prompt

Check whether ranking pages answer the task directly or only list broad prompts for product managers.
Compare whether competitors show a filled example for acceptance criteria and not just a blank prompt.
Look for missing-source risks around the user's notes, specific examples, constraints, and reviewer judgment, especially claims that need manual checking.
Verify whether the search results favors a role hub, a task page, a template page, or a tool-like prompt builder.
Confirm no volume, ranking, CPC, or difficulty number is used unless it comes from a live keyword tool export.

Why this page should match the search

For "chatgpt prompts for product managers acceptance criteria", this page should win only if the reader can turn feature goal, edge cases, roles, data states, and failure behavior into a scoring table with levels, observable evidence, and reviewer notes and still know who checks acceptance criteria.

Compare against

A broad product managers prompt collection that gives short examples without a worked criteria list with pass/fail examples.
A role guide that explains product managers work but does not turn feature goal, edge cases, roles, data states, and failure behavior into a scoring table with levels, observable evidence, and reviewer notes.
A prompt generator page that creates wording but leaves the acceptance criteria check to the user.
A task article that teaches define acceptance criteria but does not give a copyable run with a check step.

This page is stronger when

It starts from feature goal, edge cases, roles, data states, and failure behavior, then shapes the answer into a scoring table with levels, observable evidence, and reviewer notes instead of asking the reader to invent context.
It keeps the acceptance criteria check visible, so a smooth answer is not treated as ready before a person checks it.
It shows a weak-answer repair path for acceptance criteria can sound testable while states and edge cases are still missing, which is the common failure a short example misses.
It links to nearby workflows when the user really needs a different output, owner, or source note.

Outside references to open

Open the official helpful-content guidance when you need to check whether the page is solving a real user task.
Open the role-specific outside reference when product managers work needs policy, education, hiring, sales, marketing, developer, or operations context.
Keep source links beside the prompt output when the user's notes, specific examples, constraints, and reviewer judgment could change whether the answer is usable.

Improve the page when

Current search results mostly reward a different page type, such as a tool, forum thread, video, or role hub.
The top results answer a sharper question than "chatgpt prompts for product managers acceptance criteria" and this page does not yet answer that wording.
Readers cannot see criteria list with pass/fail examples before they reach a long section of explanation.
The page starts getting visits for this topic but users would still need another page to check acceptance criteria.

Check the answer before you reuse it

Who checks it

Run the human pass with the owner who would be accountable if a product team, stakeholder, customer researcher, or release owner used the answer as written.

Real-world case

acceptance criteria scenario: a field-ready version should survive a messy paste where product managers provide feature goal, edge cases, roles, data states, and failure behavior, need a scoring table with levels, observable evidence, and reviewer notes, and must keep given-when-then states, edge cases, and testable completion visible while checking the user's notes, specific examples, constraints, and reviewer judgment. For product managers, define acceptance criteria is reviewed inside a product choice workflow where evidence and tradeoffs need to stay visible, with criteria list with pass/fail examples as the concrete item on the desk.

Checks before sharing

Source review, define acceptance criteria: the answer uses the supplied feature goal, edge cases, roles, data states, and failure behavior and does not fill missing facts with confident guesses.
Output shape, define acceptance criteria: the result clearly becomes acceptance criteria, not broad advice about the task.
Handoff clarity, define acceptance criteria: the answer names missing inputs and the next human check for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Audience fit, define acceptance criteria: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and choice context.
Risk boundary, define acceptance criteria: the final version respects Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Compare with other results

Question to compare: chatgpt prompts for product managers acceptance criteria

Result acceptance criteria product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Example acceptance criteria product managers check: compare whether competing pages show a filled example for acceptance criteria using realistic feature goal, edge cases, roles, data states, and failure behavior.
Evidence acceptance criteria product managers check: mark whether each page explains how to verify the user's notes, specific examples, constraints, and reviewer judgment and acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Differentiator acceptance criteria product managers check: compare the top results against this page promise: Search edge for acceptance criteria with product managers: show criteria list with pass/fail examples, a human review path for acceptance criteria, and the task-specific reason the page deserves the query.
Failure acceptance criteria product managers check: mark whether competing pages show this failure mode or avoid it: Failure pattern for acceptance criteria with product managers: the acceptance criteria can sound polished while acceptance criteria can sound testable while states and edge cases are still missing, so the page should make that miss easy to catch.
Freshness acceptance criteria product managers check: record whether competing pages say how source notes stay current. For product managers acceptance criteria, current source notes should come first; stale or partial inputs should trigger a fresh criteria list with pass/fail examples pass instead of another saved answer.
Page type acceptance criteria product managers check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ acceptance criteria product managers check: record People Also Ask questions that should become FAQ or section coverage before publishing changes.

Do not assume

Confirm the trust pages cite official Search Central guidance for helpful content and SEO basics.
Confirm source references support the safe-use and human-review framing.
Add or keep a role-specific external reference if product managers need policy, education, developer, hiring, sales, or marketing context beyond this prompt library.
External support need: Outside support for acceptance criteria with product managers: an independent resource must mention the acceptance criteria page visibly before criteria list with pass/fail examples becomes an authority claim.

Numbers to leave out unless verified

This page can prove local readiness, source coverage, and review depth. It cannot claim ranking, traffic, search volume, CPC, or difficulty until those numbers come from search performance tool or another real search data source after publishing.

Weak prompt: too vague to trust

Help me define acceptance criteria for my work.

It gives no source material, no stakeholder, no output shape, and no review lens, so ChatGPT can fill gaps with generic advice.

Stronger prompt: specific enough to review

Help product managers define acceptance criteria by turning [source_material] into acceptance criteria for [audience]. Keep the task focus on given-when-then states, edge cases, and testable completion. Use this output shape: a scoring table with levels, observable evidence, and reviewer notes. Do not add facts beyond the source. End with a review checklist for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence and the user's notes, specific examples, constraints, and reviewer judgment.

It names the task asset, required inputs, audience, format, evidence boundary, and human review step, so the answer is easier to adapt and check.

Rewrite case from vague request to usable prompt

Original need

A PM needs criteria for sharing a prompt collection with view-only and edit access. The user needs help with acceptance criteria, but the real job is to turn a messy request into acceptance criteria that a product team, stakeholder, customer researcher, or release owner can review without hidden assumptions.

Weak prompt

Write a good acceptance criteria from this: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.

This weak version includes a real situation but gives ChatGPT no output shape, audience rule, evidence boundary, or review owner. It can sound polished while missing given-when-then states, edge cases, and testable completion, inventing details, or skipping acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Stronger prompt

Act as a careful assistant for Product Managers.
I need help with acceptance criteria. Use only this source material: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
The usual source material for this task is feature goal, edge cases, roles, data states, and failure behavior.
The audience is [audience], and the output must work for a product team, stakeholder, customer researcher, or release owner.
Create acceptance criteria in this shape: a scoring table with levels, observable evidence, and reviewer notes.
Keep the task focus on given-when-then states, edge cases, and testable completion.
Respect this editorial rule: The prompt must turn vague requirements into observable behavior without prescribing code.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, the user's notes, specific examples, constraints, and reviewer judgment, and this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

The stronger version gives ChatGPT a role, real input, audience, output shape, editorial boundary, and review lens. It also forces missing-context questions before creation and keeps the user's notes, specific examples, constraints, and reviewer judgment visible for human checking.

Sample input

A PM needs criteria for sharing a prompt collection with view-only and edit access. User notes: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access. Audience: a product team, stakeholder, customer researcher, or release owner. Constraints: avoid unsupported claims, protect private details, and keep focus on given-when-then states, edge cases, and testable completion.

Example answer shape

A useful answer starts by restating the real situation, then provides a scoring table with levels, observable evidence, and reviewer notes. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, the user's notes, specific examples, constraints, and reviewer judgment, and this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. The output should already reflect the practical review target that matters here, so the final criteria should be unambiguous enough for engineering and QA review.

Human-edited final version

The human keeps the structure, removes any unsupported claim, adds missing facts from the real source, and saves the prompt as a reusable acceptance criteria prompt pattern with source notes, constraints, and review checklist. Before sharing with a product team, stakeholder, customer researcher, or release owner, the final pass checks tone, privacy, evidence, and whether given-when-then states, edge cases, and testable completion is still the center of the answer. The pass is accepted only when the final criteria should be unambiguous enough for engineering and QA review.

Fit

Use when product managers have real source notes for acceptance criteria.
Use when the desired result is acceptance criteria, not broad advice.
Use when a human can review acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence before the output reaches a product team, stakeholder, customer researcher, or release owner.

Not fit

Do not use when the model is expected to invent facts, numbers, credentials, or private details.
Do not use when the user's notes, specific examples, constraints, and reviewer judgment is unavailable and cannot be checked.
Do not use as final judgment for sensitive outcomes covered by this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Worked example: Define acceptance criteria example from rough notes

Example input

A PM needs criteria for sharing a prompt collection with view-only and edit access. Raw input: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.

Prompt use

Use the evidence-aware prompt to convert those notes into acceptance criteria, then run the review prompt against this editorial rule: The prompt must turn vague requirements into observable behavior without prescribing code.

What the answer should look like

A useful answer would return a scoring table with levels, observable evidence, and reviewer notes for a product team, stakeholder, customer researcher, or release owner, while making the source details and assumptions visible. It should preserve the real constraint in the input, keep given-when-then states, edge cases, and testable completion at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially the user's notes, specific examples, constraints, and reviewer judgment. The human pass is not decoration here: The final criteria should be unambiguous enough for engineering and QA review.

Review notes

Confirm the answer reflects this actual situation: A PM needs criteria for sharing a prompt collection with view-only and edit access.
Compare the output against the raw user input: Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access.
Confirm the source material really supports the user's notes, specific examples, constraints, and reviewer judgment.
Check that the wording fits a product team, stakeholder, customer researcher, or release owner.
Confirm the answer handles given-when-then states, edge cases, and testable completion instead of a neighboring task.
Remove details that violate this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Build and check the prompt

advanced

Fill this prompt for the current run

Filled prompt preview

Run this evidence-aware working copy prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: feature goal, edge cases, roles, data states, and failure behavior. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: a product team, stakeholder, customer researcher, or release owner. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: given-when-then states, edge cases, and testable completion. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: make acceptance criteria easier to review, adapt, and use in a real product managers workflow. Constraints: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to feature goal, edge cases, roles, data states, and failure behavior, and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a scoring table with levels, observable evidence, and reviewer notes.
Before writing acceptance criteria, ask up to 3 clarifying questions when feature goal, edge cases, roles, data states, and failure behavior does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a working version they can inspect against the supplied notes.

beginner

Define acceptance criteria for product manager Context Intake Prompt

Use this before acceptance criteria when the notes are rough and ChatGPT should ask clarifying questions first.

Run this context intake prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as intake: ask the questions needed before writing, then wait for answers if the source material is missing.
Stop rule: Stop before creating the final asset if the audience, source material, or review owner is unclear.
Return a question list grouped by audience, source material, constraints, and review owner.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should leave with a short context pack and a safe next prompt, not a finished answer.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a question list grouped by audience, source material, constraints, and review owner that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Now improve this working version into acceptance criteria by tightening acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence, emphasizing given-when-then states, edge cases, and testable completion, removing unsupported claims, and giving me one stronger version for a product team, stakeholder, customer researcher, or release owner.

Human review

Check whether the answer uses only provided context, handles the user's notes, specific examples, constraints, and reviewer judgment, fits a product team, stakeholder, customer researcher, or release owner, reflects given-when-then states, edge cases, and testable completion, and respects this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Best for: Starting acceptance criteria when the source material still needs shape. Use when: Use before asking ChatGPT for acceptance criteria so the model has enough task-specific context.

advanced

Define acceptance criteria for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become acceptance criteria.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a scoring table with levels, observable evidence, and reviewer notes that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Turning prepared context into acceptance criteria. Use when: Use before asking ChatGPT for acceptance criteria so the model has enough task-specific context.

workflow

Define acceptance criteria for product manager Repeatable Workflow Prompt

Use this when acceptance criteria repeats often enough to become acceptance criteria prompt pattern with source notes, constraints, and review checklist.

Run this repeatable workflow prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as a repeatable workflow: separate one-time facts from fields that should change next time.
Stop rule: Stop if the reusable version would preserve private details or hide a human approval step.
Return a reusable step-by-step workflow with inputs, checks, and follow-up prompts.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get reusable fields, a run order, and a reject-if rule for the next use.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a reusable step-by-step workflow with inputs, checks, and follow-up prompts that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Creating a reusable process for repeated acceptance criteria. Use when: Use when acceptance criteria repeats often enough to need a standard process.

review

Define acceptance criteria for product manager Human Review Prompt

Use this after there is already working copy and the main need is acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Run this human review prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as a review of existing copy: score the answer, name the weak sections, and propose repairs.
Stop rule: Stop if the copy cannot be traced back to the supplied source material or the reviewer is not named.
Return a scored review table with issues, fixes, and what still needs human judgment.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a choice about accept, repair, or reject before polishing the wording.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a scored review table with issues, fixes, and what still needs human judgment that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Finding weak spots in existing working copy. Use when: Use after product managers already have working copy and need to check acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

format

Define acceptance criteria for product manager Format Conversion Prompt

Use this when the substance is right but the output needs to fit a table, checklist, email, outline, or script.

Run this format conversion prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as format conversion: preserve the facts and change only the structure, order, or channel fit.
Stop rule: Stop if the requested format would require adding facts that were not in the original answer.
Return the same content reshaped without adding new facts.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a reshaped version plus a note showing what stayed unchanged.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect the same content reshaped without adding new facts that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Changing the output format without changing the facts. Use when: Use when the answer needs a precise structure before product managers can review it.

privacy

Define acceptance criteria for product manager Privacy-Safe Prompt

Use this when the source material contains private, sensitive, or account-specific details.

Run this privacy-safe prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as a sanitizing pass: replace private details with role-safe descriptions before writing.
Stop rule: Stop if names, identifiers, account details, confidential strategy, or one-time records are still present.
Return a sanitized prompt-ready summary plus a list of removed details.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a safe summary, removed-detail list, and a reusable version without sensitive data.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a sanitized prompt-ready summary plus a list of removed details that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Sanitizing context before asking ChatGPT for help. Use when: Use before adding sensitive context so private details stay out.

short

Define acceptance criteria for product manager Fast Checklist Prompt

Use this for a quick pass when the user only needs the next few choices for acceptance criteria.

Run this fast checklist prompt for Product Managers; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with acceptance criteria. Target result: acceptance criteria.
Source material I can provide: [source_material]. Typical source for this task is feature goal, edge cases, roles, data states, and failure behavior.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: given-when-then states, edge cases, and testable completion.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the user's notes, specific examples, constraints, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for acceptance criteria: Run this as a fast choice pass: give only the next actions, the missing input, and the main risk.
Stop rule: Stop if the user needs a full artifact, a legal answer, a policy choice, or unsupported factual claims.
Return a concise checklist with the next action and the main risk.
Before writing acceptance criteria, ask up to 3 clarifying questions when [source_material] does not include feature goal, edge cases, roles, data states.
After the answer, include a human review section focused on [review_lens]. Verify the user's notes, specific examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for acceptance criteria, The user should get a narrow next step they can complete before opening a longer prompt.

[source_material]: Paste the concrete product manager acceptance criteria notes, such as feature goal, edge cases, roles, data states, and failure behavior.Example: feature goal, edge cases, roles, data states, and failure behavior
[audience]: Who will read, use, approve, or act on this product manager acceptance criteria.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager acceptance criteria run should support.Example: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager acceptance criteria: tone, length, channel, privacy, and the user's notes, specific examples, constraints, and reviewer.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use support.Example: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager acceptance criteria prompt specific: given-when-then states, edge cases, and testable completion.Example: given-when-then states, edge cases, and testable completion

Expected output

Expect a concise checklist with the next action and the main risk that explicitly separates source-based content from assumptions and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Follow-up prompt

Human review

Best for: Getting a quick choice checklist before spending more time. Use when: Use when time is short and the user needs the next action, not a full answer.

Variables

[source_material]: feature goal, edge cases, roles, data states, and failure behavior
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make acceptance criteria easier to review, adapt, and use in a real product managers workflow
[constraints]: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence
[task_focus]: given-when-then states, edge cases, and testable completion

Answer checks

Context: Does the prompt give enough feature goal, edge cases, roles, data states, and failure behavior to avoid guessing?
Specificity: Does the answer produce acceptance criteria rather than broad advice?
Task focus: Does it handle given-when-then states, edge cases, and testable completion instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check acceptance criteria checkpoint and the user's notes, specific examples, constraints, and reviewer judgment?
Fit: Does the wording match a product team, stakeholder, customer researcher, or release owner and the real channel?
Safety: Are private details, unsupported claims, and policy-sensitive assumptions controlled?

Common mistakes

Asking ChatGPT to define acceptance criteria without giving feature goal, edge cases, roles, data states, and failure behavior.
Accepting polished wording before checking the user's notes, specific examples, constraints, and reviewer judgment.
Using the same prompt for every product manager task instead of changing the output shape and review lens.
Forgetting to name a product team, stakeholder, customer researcher, or release owner, which makes tone and detail level drift.
Ignoring the task-specific focus: given-when-then states, edge cases, and testable completion.
Skipping the review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.
Pasting private or sensitive details when a summarized version would work.

Before you share

Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Ask ChatGPT to label assumptions and verification needs before using acceptance criteria.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that given-when-then states, edge cases, and testable completion is supported by the source material and not invented.
Have a human review acceptance criteria checkpoint before sharing the output with a product team, stakeholder, customer researcher, or release owner.

FAQ

What is the best prompt for product managers to define acceptance criteria?

Use a prompt that names feature goal, edge cases, roles, data states, and failure behavior, asks for a scoring table with levels, observable evidence, and reviewer notes, and ends with a review pass for acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

What should I paste into ChatGPT first?

Paste sanitized source notes, the intended audience, constraints, and the choice the output must support. For this task, the key input is feature goal, edge cases, roles, data states, and failure behavior.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against the user's notes, specific examples, constraints, and reviewer judgment and a product team, stakeholder, customer researcher, or release owner.

What should a human check before using the output?

Check facts, tone, privacy, unsupported claims, and the task-specific lens: acceptance criteria quality, given-when-then states and edge cases, and ready-to-use evidence.

Next workflows

ChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.
Write PRDsUseful next step when this workflow needs a related product managers output or review pass.
Write user storiesUseful next step when this workflow needs a related product managers output or review pass.
Prioritize roadmapsUseful next step when this workflow needs a related product managers output or review pass.
Structure competitor analysisUseful next step when this workflow needs a related product managers output or review pass.
Write release notesUseful next step when this workflow needs a related product managers output or review pass.

Define Acceptance Criteria: start from feature goal and edge cases

Start with the note you actually have1/3 ready

Copy this after checking the notes

Check the answer before saving it

Pick accept, repair, or reject before reuse

Save the answer, problem, and next try

Save the final answer, human edit, and variables

Set up the first run

Define acceptance criteria for product manager Evidence-Aware Working Copy Prompt

Variable Builder

Copy this filled version

Run this page in four moves

Start from the real note, not a blank prompt

Check the answer against your note

Real use plan for treating the prompt like a work note

Before copying

After ChatGPT answers

Reject the answer if

Choose the next move

Build The Asset

Know when the answer is ready

Ready signal

First run action

Second pass before the answer becomes reusable

Source line

Human check note

the rough note "Need Given-When-Then criteria, permissions, empty states, errors, activity log events, and edge cases for revoked access" as the visible source line for acceptance criteria

any confident claim about the user's notes, specific examples, constraints, and reviewer judgment that the pasted note does not prove

the missing audience, owner, or review detail needed before a product team, stakeholder, customer researcher, or release owner uses the answer

the first polished paragraph so it shows given-when-then states, edge cases, and testable completion before tone improvements

Why this feels hand-edited

Run the second pass

Task actions for the next useful move

Before you use the answer, make the call

Working case file: Define Acceptance Criteria working case for Product Managers

Rough note

Constraint to keep visible

What the user brought

What is still missing

Who accepts the answer

What gets saved

Before copying

Checks before sharing

Run this case first

Input triage before running ChatGPT

Missing context

Notes to save before reusing this prompt

Details copied from the user's case

Guesses that need a review line

Boundaries that decide readiness

Sensitive context to keep out

Items that should become blanks

Iteration loop: run the prompt as a working thread

Thread goal

Working pass

Missing support pass

Reviewer challenge

Final pass

Prompt readiness check before you copy

Collect context first

Session handoff: finish the run without losing the thread

Collect working context

Work note: what the rough note changes

Original working note

Questions before reuse

Who checks it

Usable output

Prompt run from pasted notes

Pasted notes

Why this input is messy

First prompt move

Questions ChatGPT should ask

Usable answer shape

Human revision

Save or discard

Choose the right workflow for this job

Work moment

Why this workflow

Do first

Next best workflow