Write User Stories: review user stories

For user stories, bring the rough note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and turn it into user stories with job situation, user motivation, acceptance signal, and slice size visible from the first pass.

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

First move: Start user stories only after the audience, source material, stop rule, and reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence are named; otherwise collect context before copying.
Keep after run: Keep after the user stories run: the original note, the variables that changed the answer, and the section where the actual notes, usable examples, boundary checks, and reviewer judgment is separated from assumptions before reuse.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for Product Managers if the user cannot supply user segment, job, pain, desired outcome, and acceptance signals, if the desired result is not user stories, or if job situation, user motivation, acceptance signal, and slice size 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 write user stories run

Messy input: A rough user stories note comes in: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." is the rough request. Before reusing user stories, the usable version reads as user stories, keeps job situation, user motivation, acceptance signal, and slice size visible, names the checker, and protects this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Better answer should: A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.
Human edit: product manager should revise the user stories answer by keeping the parts that saved review time, make each reusable section point back to the source note inside user stories, replace private or one-off details with reusable fields, and shape the closing version for a product team, stakeholder, customer researcher, or release owner; check it against "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep this final standard visible: the final stories should be testable, scoped, and traceable to user evidence.

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 ruleUse the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse. must know what to reject before the answer is reused.

Real note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
What will change: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.
Human check: Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals 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 Write User Stories
Who checks it: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

Paste source notes:
Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.

Must keep:
Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
user segment, job, pain, desired outcome, and acceptance signals
job situation, user motivation, acceptance signal, and slice size

Do not allow:
Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Reject it if the output sounds polished but does not become user stories.

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: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse. 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories with the usable answer first, then gaps and follow-up checks.
Before writing user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a working version they can inspect against the supplied notes.

Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Record to keep: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories 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, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals and does not fill missing facts with confident guesses. Output shape, write user stories: the result clearly becomes user stories, not broad advice about the task.
Reject if: Evidence issue, write user stories: the answer invents or overstates the actual notes, usable examples, boundary checks, and reviewer judgment. Task drift, write user stories: it ignores job situation, user motivation, acceptance signal, and slice size and moves into a neighboring workflow.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories 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 write user stories answer, the product manager should choose Accept, Repair, or Reject before saving anything as user stories prompt pattern with source notes, constraints, and review checklist. The choice must compare "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." with user stories with the usable answer first, then gaps and follow-up checks, job situation, user motivation, acceptance signal, and slice size, and the actual notes, usable examples, boundary checks, and reviewer judgment.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: job situation, user motivation, acceptance signal, and slice size, the actual notes, usable examples, boundary checks, and reviewer judgment, the reviewer role, the source note, or the reusable fields needed for user stories 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 user stories in user stories with the usable answer first, then gaps and follow-up checks without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed user stories quality, job situation and user motivation, and ready-to-use evidence, and save the corrected line only after it can be traced back to "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.".

Answer choice prompt

Repair this write user stories answer instead of accepting it. Source note: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide job situation, user motivation, acceptance signal, and slice size, turn the actual notes, usable examples, boundary checks, and reviewer judgment into unsupported certainty, or skip the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence. Return a repaired user stories with the usable answer first, then gaps and follow-up checks, a list of changed lines, and one remaining question before this can become user stories prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable user stories prompt pattern with source notes, constraints, and review checklist until one option has a written choice. The saved version must keep "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." 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 Write User Stories before it is saved, shared, or reused.
Reuse rule: Reuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.
Saved: 0/3 checks

Saved version preview

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

Save only after review:
- Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals and does not fill missing facts with confident guesses.
- Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories prompt pattern with source notes, constraints, and review checklist.
- Store the source note, the fields that changed the output, the checked line, and the reason the result belongs with a product team, stakeholder, customer researcher, or release owner.
- Current answer choice: Keep the weak answer beside the repair note, mark which line failed user stories quality, job situation and user motivation, and ready-to-use evidence, and save the corrected line only after it can be traced back to "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.".

Source note used:
Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.

Final answer:
A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.

Human edit:
product manager should revise the user stories answer by keeping the parts that saved review time, make each reusable section point back to the source note inside user stories, replace private or one-off details with reusable fields, and shape the closing version for a product team, stakeholder, customer researcher, or release owner; check it against "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep this final standard visible: the final stories should be testable, scoped, and traceable to user evidence.

Reusable variables:
[source_material]: user segment, job, pain, desired outcome, and acceptance signals
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make user stories 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: Reuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.
Stop if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

First run setup

Set up the first run

Edit notes

First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.
Bring first: Bring the rough case note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
Switch if: The user cannot provide user segment, job, pain, desired outcome, and acceptance signals and would need ChatGPT to invent the important facts.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories 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 user stories prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps user stories quality, job situation and user motivation, and ready-to-use evidence and the actual notes, usable examples, boundary checks, and reviewer judgment visible before sharing anything. Start with: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.

Go to runner

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

Who checks it

Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

Check before using

Inspect user segment, job, pain, desired outcome, and acceptance signals, the case note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", and any open support around the actual notes, usable examples, boundary checks, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

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

Visitor question: I have user segment, job, pain, desired outcome, and acceptance signals and need user stories for a product team, stakeholder, customer researcher, or release owner; can this write user stories page turn "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." into user stories with the usable answer first, then gaps and follow-up checks without hiding job situation, user motivation, acceptance signal, and slice size?
5-minute outcome: Within five minutes, the user should have a first user stories prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps user stories quality, job situation and user motivation, and ready-to-use evidence and the actual notes, usable examples, boundary checks, 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 job situation, user motivation, acceptance signal, and slice size is not the controlling choice, or if the user only wants broad ideas instead of a reviewable user stories.
Why this workflow fits: Save the rough note, the accepted prompt variables, the user stories query language, and the section that shows why this user stories should stay separate from ChatGPT Prompts for Product Managers.
Reuse choice: Reuse the output only when the answer traces back to user segment, job, pain, desired outcome, and acceptance signals, 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? ChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.

Working brief

Check the job before copying

This workflow earns its own place because the source has to become user stories, and the acceptance test is whether a product team, stakeholder, customer researcher, or release owner can use it without guessing the missing pieces.

Use this when: The page is for the moment when product managers have enough notes to create user stories, but still need a choice about job situation, user motivation, acceptance signal, and slice size.
Paste this kind of note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
Expected result: A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.
Stop before reuse if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Human check: Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
Build when: Use this when the notes are ready and the next useful output is user stories with the usable answer first, then gaps and follow-up checks, 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 user stories.
Users who want ChatGPT to ask clarifying questions before it commits to user stories with the usable answer first, then gaps and follow-up checks.
Teams that repeat user stories 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?ChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.

Editorial method Safe use About this library

Write user stories for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become user stories.

Real input: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
Target output: A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.
Reject if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Scenario: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The user stories work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. For user stories work, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a product manager checks first.
Bring: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. user segment, job, pain, desired outcome, and acceptance signals job situation, user motivation, acceptance signal, and slice size
Check: The final stories should be testable, scoped, and traceable to user evidence. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. Before handing off the user stories, the final human edit should keep the useful structure, remove unsupported details, add verified context, and check user stories quality, job situation and user motivation, and ready-to-use evidence before the output reaches a product team, stakeholder, customer researcher, or release owner. Keep a short record of what changed before reuse. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

Variable Builder

[source_material]Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.[audience]Who will read, use, approve, or act on this product manager user stories.[goal]The choice or work outcome this product manager user stories run should support.[constraints]Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.[review_lens]Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.[task_focus]The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.

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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories with the usable answer first, then gaps and follow-up checks.
Before writing user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a working version they can inspect against the supplied notes.

Show the full prompt

Expected output: Expect user stories with the usable answer first, then gaps and follow-up checks that explicitly separates source-based content from assumptions and ends with a review pass for user stories quality, job situation and user motivation, and ready-to-use evidence.

First run

Run this page in four moves

Concrete outputA usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.

Keep after runSave a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories prompt pattern with source notes, constraints, and review checklist.

Reject before reuseReject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

PrepareCollect ContextUse this when the product manager source notes are still uneven or missing the detail that would shape user stories.CopyBuild The AssetUse this when the notes are ready and the next useful output is user stories with the usable answer first, then gaps and follow-up checks, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before user stories quality, job situation and user motivation, 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.
Who checks it: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.CopyBuild The AssetExpect user stories with the usable answer first, then gaps and follow-up checks that explicitly separates source-based content from assumptions and ends with a review pass for user stories quality, job situation and user motivation, and ready-to-use evidence.GradeReview The AnswerCompare the answer against the original notes and mark every line that depends on the actual notes, usable examples, boundary checks, and reviewer judgment.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 job situation, user motivation, acceptance signal, and slice size.
Human check: Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals 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 user stories

Open reference checks

Paste into ChatGPT: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
Question to compare: chatgpt prompts for product managers user storiesResult user stories 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 user stories needs human oversight, assumptions, and review controls.
Who checks it: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.Inspect user segment, job, pain, desired outcome, and acceptance signals, the case note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", and any open support around the actual notes, usable examples, boundary checks, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Use this user stories page when product managers already have user segment, job, pain, desired outcome, and acceptance signals and need the answer to become user stories, not a loose idea list. The prompt should ask for user segment, job, pain, desired outcome, and acceptance signals, the audience, the intended channel, and the constraints before it tries to format the result. user stories artifact check: inspect story set with acceptance signals before accepting the answer. Accept the answer only when user stories quality, job situation and user motivation, and ready-to-use evidence can be checked and the open questions are visible. Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Before using the output, run the follow-up prompt and check the result against the real context for a product team, stakeholder, customer researcher, or release owner.

Real use plan for treating the prompt like a work note

0/12 checked

The write user stories plan starts with the rough note, then forces a check against user stories quality, job situation and user motivation, and ready-to-use evidence before user stories reaches a product team, stakeholder, customer researcher, or release owner; that keeps the useful structure while making unsupported claims easy to reject.

Before copying

Paste the messy notes first: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.Name the real audience for user stories: a product team, stakeholder, customer researcher, or release owner, plus the channel, deadline, or approval point.Add the non-negotiable constraint from this case: The prompt must keep user value separate from solution details.Keep the task narrow by naming job situation, user motivation, acceptance signal, and slice size before asking for user stories with the usable answer first, then gaps and follow-up checks.

After ChatGPT answers

Compare the answer against the original notes and mark every line that depends on the actual notes, usable examples, boundary checks, and reviewer judgment.Keep source-backed sections separate from assumptions so user stories quality, job situation and user motivation, and ready-to-use evidence can be checked quickly.Ask one follow-up only after the first answer proves it understood job situation, user motivation, acceptance signal, and slice size.Turn the accepted answer into user stories prompt pattern with source notes, constraints, and review checklist only after removing one-time names and details.

Reject the answer if

Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.Reject it if the output sounds polished but does not become user stories.Reject it if Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. is handled as a style note instead of a hard boundary.Reject it if the final stories should be testable, scoped, and traceable to user evidence. cannot be verified by a human reviewer.

Choose the next move

Start by turning the rough request into named fields before asking for user stories.

Build The Asset

Use this when the notes are ready and the next useful output is user stories with the usable answer first, then gaps and follow-up checks, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for user stories with assumptions separated from source-backed details.
Bring first: Bring the task focus: job situation, user motivation, acceptance signal, and slice size. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete user stories.
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

Paste the messy notes first: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
Name the real audience for user stories: a product team, stakeholder, customer researcher, or release owner, plus the channel, deadline, or approval point.
Add the non-negotiable constraint from this case: The prompt must keep user value separate from solution details.

Accept only if

Compare the answer against the original notes and mark every line that depends on the actual notes, usable examples, boundary checks, and reviewer judgment.
Keep source-backed sections separate from assumptions so user stories quality, job situation and user motivation, and ready-to-use evidence can be checked quickly.
Ask one follow-up only after the first answer proves it understood job situation, user motivation, acceptance signal, and slice size.

Reject when

Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

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

Finish the run only when the pasted request "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." becomes user stories with named sections, action bullets, and a final reviewer pass, keeps job situation, user motivation, acceptance signal, and slice size visible, and gives the person approving user stories a named accept, revise, or discard call before sharing with a product team, stakeholder, customer researcher, or release owner.

First run action

Open with the rough note user segment, job, pain, desired outcome, and acceptance signals, the intended user stories, the audience, the stop rule "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided", and the support needed for the actual notes, usable examples, boundary checks, and reviewer judgment.

Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs user stories quality, job situation and user motivation, and ready-to-use evidence, and the final reason the accepted version can become user stories prompt pattern with source notes, constraints, and review checklist.
Use or revise: the person approving user stories should approve the output only if it can be traced back to user segment, job, pain, desired outcome, and acceptance signals, shows what is assumed, and does not turn the actual notes, usable examples, boundary checks, and reviewer judgment into a confident claim without review.
What makes this page different: This page can beat a short generic collection by tying the query "chatgpt prompts for product managers user stories" 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 user stories query because user stories changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby product manager page would hide job situation, user motivation, acceptance signal, and slice size and weaken the final user stories.

Second pass

Second pass before the answer becomes reusable

Source line

Editor margin source for user stories: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." It is the sentence most likely to disappear when a smooth answer starts too quickly.

Human check note

a working editor checking user stories quality, job situation and user motivation, and ready-to-use evidence reads the first ChatGPT answer beside the rough note and decides what survives. The pass is intentionally narrow: preserve the note, remove unsupported confidence, ask for the missing support, then rewrite only the part that changes the choice. The check belongs before the prompt is saved as user stories prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out" as the visible source line for user stories

Keep this because the rough note is the only part a product manager can compare against the answer when user stories with the usable answer first, then gaps and follow-up checks starts to sound finished.

The accepted answer should repeat or clearly map back to "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." before it adds structure.

Cut

any confident claim about the actual notes, usable examples, boundary checks, and reviewer judgment that the pasted note does not prove

Cut it because the support around the actual notes, usable examples, boundary checks, 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 user stories 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 job situation, user motivation, acceptance signal, and slice size before tone improvements

Rewrite the opening because this task is about job situation, user motivation, acceptance signal, and slice size, not a general user stories answer that could fit any role page.

A reviewer should see job situation, user motivation, acceptance signal, and slice size in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

a working editor checking user stories quality, job situation and user motivation, and ready-to-use evidence leaves this margin pass because the workflow has to protect a real source note, not only offer another prompt. For product managers working on user stories, the human-feeling part is the specific tradeoff: keep "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around job situation, user motivation, acceptance signal, and slice size. 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." Output being reviewed: [paste ChatGPT answer]. Mark four choices: Keep the source-backed detail that should survive, Cut any unsupported claim about the actual notes, usable examples, boundary checks, 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 job situation, user motivation, acceptance signal, and slice size stays visible before polish. End with one accept, repair, or reject choice and a reuse rule for user stories prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.

CollectCollect ContextBring the rough case note: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.CopyBuild The AssetExpect user stories with the usable answer first, then gaps and follow-up checks that explicitly separates source-based content from assumptions and ends with a review pass for user stories quality, job situation and user motivation, and ready-to-use evidence.CheckReview The AnswerCompare the answer against the original notes and mark every line that depends on the actual notes, usable examples, boundary checks, and reviewer judgment.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 user segment, job, pain, desired outcome, and acceptance signals and would need ChatGPT to invent the important facts.

Stay hereThe page is for the moment when product managers have enough notes to create user stories, but still need a choice about job situation, user motivation, acceptance signal, and slice size. First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for user stories quality, job situation and user motivation, and ready-to-use evidence.

Switch ifChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.

Stop ifThe user cannot provide user segment, job, pain, desired outcome, and acceptance signals and would need ChatGPT to invent the important facts. The desired result is not user stories or cannot be shaped as user stories with the usable answer first, then gaps and follow-up checks.

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: Before handoff, the person deciding whether this becomes user stories prompt pattern with source notes, constraints, and review checklist compares the answer with the rough case note for user stories and decides what can reach a product team, stakeholder, customer researcher, or release owner.
Check before using: Inspect user segment, job, pain, desired outcome, and acceptance signals, the case note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", and any open support around the actual notes, usable examples, boundary checks, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: The user should leave judging readiness, not shopping for wording: does this user stories show job situation, user motivation, acceptance signal, and slice size, name what came from user segment, job, pain, desired outcome, and acceptance signals, and give a product team, stakeholder, customer researcher, or release owner a clear next step?
Do next: The final stories should be testable, scoped, and traceable to user evidence. Then save only the repeatable fields, not the one-time case details, so the next run still asks for user stories quality, job situation and user motivation, 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 user stories" and record where it came from.

Working case file: Write User Stories working case for Product Managers

This is the work moment before a product manager should copy the prompt. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps user segment, job, pain, desired outcome, and acceptance signals, user stories with the usable answer first, then gaps and follow-up checks, and the person approving user stories in the same run.

Rough note

A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The rough note says: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." The desired result is user stories for a product team, stakeholder, customer researcher, or release owner.

Constraint to keep visible

The answer has to protect job situation, user motivation, acceptance signal, and slice size before it improves wording. 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", so the answer should begin from the user's actual wording and not from broad write user stories advice.

The finished user stories should point back to user segment, job, pain, desired outcome, and acceptance signals and show how job situation, user motivation, acceptance signal, and slice size changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any support needed for the actual notes, usable examples, boundary checks, 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 person approving user stories should inspect user stories quality, job situation and user motivation, 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 job situation, user motivation, acceptance signal, and slice size.

One-time details should be removed only after the accepted answer proves that user stories with the usable answer first, then gaps and follow-up checks works for this case.

Before copying

Can the user point to the exact user segment, job, pain, desired outcome, and acceptance signals ChatGPT is allowed to use?
Is job situation, user motivation, acceptance signal, and slice size visible before the prompt asks for user stories?
Has the user named the reviewer who checks user stories quality, job situation and user motivation, and ready-to-use evidence?
Is there a stop rule for unsupported claims about the actual notes, usable examples, boundary checks, and reviewer judgment?

Checks before sharing

Compare the first answer with "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and mark any section that invents context.
Check whether the output is shaped as user stories with the usable answer first, then gaps and follow-up checks, 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 user stories 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." Build user stories as user stories with the usable answer first, then gaps and follow-up checks. Keep job situation, user motivation, acceptance signal, and slice size visible, separate supplied facts from assumptions, ask for missing support around the actual notes, usable examples, boundary checks, and reviewer judgment, name the person approving user stories as the checker, and stop before using any claim that the source notes do not support.

Ready means the result can move to a product team, stakeholder, customer researcher, or release owner with supplied notes, assumptions, and checks still separated. 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 write user stories run before a product team, stakeholder, customer researcher, or release owner can use it?

Selected issue

Missing context

Build context

Symptom: Write User Stories starts from a rough note like "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." 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 user stories decide?
Do next: Start by rewriting the rough note into named fields before asking for user stories with the usable answer first, then gaps and follow-up checks, then confirm the reviewer can inspect each field.
Prompt move: Before writing, ask me up to four questions needed to produce user stories with the usable answer first, then gaps and follow-up checks; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind job situation, user motivation, acceptance signal, and slice size.
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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." before running write user stories 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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run checks before a product team, stakeholder, customer researcher, or release owner sees story set with acceptance signals. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

Supplied context that should stay visible

Capture: Capture the concrete case first: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The note says "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and the requested asset is story set with acceptance signals. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.
Keep: Keep the facts that directly affect user stories with the usable answer first, then gaps and follow-up checks, especially the audience, task focus, channel, and any details already present in user segment, job, pain, desired outcome, and acceptance signals.
Verify: Verify that every useful line in the answer can point back to the rough note or to user segment, job, pain, desired outcome, and acceptance signals.
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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run checks whether the answer still reflects user stories quality, job situation and user motivation, and ready-to-use evidence after the first pass.
If skipped: If this row is skipped, user stories can sound specific while drifting into generic write user stories advice.

Unverified points to keep separate

Capture: List what the user did not provide but the answer may need: missing audience detail, missing support around the actual notes, usable examples, boundary checks, 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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run 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 job situation, user motivation, acceptance signal, and slice size.

Stop rules for the first pass

Capture: Record the rule from this case: The prompt must keep user value separate from solution details. Also include Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. and this field friction before the model writes: user stories can mention users without preserving job context and acceptance signals. Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.
Keep: Keep the constraint near the requested format so it governs the whole user stories with the usable answer first, then gaps and follow-up checks, 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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run 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.

Information that should not become a template

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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run confirms that the final user stories 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.

Fields to preserve across future use

Capture: Name the fields that should change next time: source notes, audience, output format, support needed for the actual notes, usable examples, boundary checks, and reviewer judgment, reviewer, and stop rule.
Keep: Keep job situation, user motivation, acceptance signal, and slice size, user stories quality, job situation and user motivation, and ready-to-use evidence, and story set with acceptance signals as required fields so the saved prompt does not collapse into a generic role prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals 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 person saving user stories prompt pattern with source notes, constraints, and review checklist for the next run 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 user stories 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 job situation, user motivation, acceptance signal, and slice size, and the place where user stories can mention users without preserving job context and acceptance signals. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. Outside support for user stories with product managers: an independent resource must mention the user stories page visibly before story set with acceptance signals becomes an authority claim.

Iteration loop: run the prompt as a working thread

Write User Stories works best as a short conversation, not as one copy action. Start from the rough note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", then ask ChatGPT to write, question, challenge, and hand off story set with acceptance signals without hiding the actual notes, usable examples, boundary checks, and reviewer judgment. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

Thread goal

Thread goal for product manager: turn the rough case from A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. into user stories with the usable answer first, then gaps and follow-up checks for a product team, stakeholder, customer researcher, or release owner, while the reviewer accountable for user stories quality, job situation and user motivation, and ready-to-use evidence can still inspect user stories quality, job situation and user motivation, and ready-to-use evidence, job situation, user motivation, acceptance signal, and slice size, unsupported assumptions, and the friction that user stories can mention users without preserving job context and acceptance signals. Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.

Write User Stories is finished only when the handoff names what is ready, what still needs checking, and which fields become variables next time. 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 story set with acceptance signals as finished. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.

1
First run
Use this first when the source note is messy but concrete enough to produce a reviewable user stories.
```
Write User Stories first run: use the rough note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." from A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects.; build user stories as user stories with the usable answer first, then gaps and follow-up checks; rely on supplied facts for the main answer, label assumptions, keep job situation, user motivation, acceptance signal, and slice size visible, and end with the support still needed for the actual notes, usable examples, boundary checks, and reviewer judgment.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports job situation, user motivation, acceptance signal, and slice size.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the reviewer accountable for user stories quality, job situation and user motivation, and ready-to-use evidence something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats the actual notes, usable examples, boundary checks, and reviewer judgment as proven, or drifts into general write user stories advice.
2
Gap fill
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Write User Stories 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 user segment, job, pain, desired outcome, and acceptance signals; 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 user stories with the usable answer first, then gaps and follow-up checks, user stories quality, job situation and user motivation, and ready-to-use evidence, or the final handoff.
3
Skeptic pass
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Write User Stories 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 actual notes, usable examples, boundary checks, and reviewer judgment; give each issue a repair sentence that keeps job situation, user motivation, acceptance signal, and slice size 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 reviewer accountable for user stories quality, job situation and user motivation, and ready-to-use evidence 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
Handoff
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Write User Stories handoff: prepare the accepted user stories, a needs-checking block for the actual notes, usable examples, boundary checks, and reviewer judgment, a reviewer note for the reviewer accountable for user stories quality, job situation and user motivation, and ready-to-use evidence, and a reusable version with variables for source notes, audience, output format, support need, stop rule, and job situation, user motivation, acceptance signal, and slice size; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair choices, and the variables that make user stories 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.Audience or recipient knownProduct Managers who have real notes or context and need a structured first version of user stories.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 user stories.Facts to verify listedUser Stories reader check: who will read or approve this user stories, and what do they already know? User Stories source sort: which lines in the rough note are facts, preferences, constraints, or open questions?Checker is namedUse the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.Reuse rule clearReuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals 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 user stories.
Wait if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Who checks it: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.
Reuse rule: Reuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.
Who checks it: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.
Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Reuse choice: Reuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals 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

A rough user stories note comes in: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." is the rough request. Before reusing user stories, the usable version reads as user stories, keeps job situation, user motivation, acceptance signal, and slice size visible, names the checker, and protects this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Received note: Received note for Product Managers Write User Stories: "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." arrives as the source note inside a product choice workflow where evidence and tradeoffs need to stay visible, with The prompt must keep user value separate from solution details. as the first human concern and story set with acceptance signals as the target artifact.
Question before run: Before the first run, ask which part of "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." is fixed source material and which part is only preference, guesswork, or a missing approval point for the person who will approve user stories.
First answer flaw: First answer flaw for Product Managers Write User Stories: the first answer may sound polished while it drops the rough-note constraint, skips the reviewer, and turns the actual notes, usable examples, boundary checks, and reviewer judgment into an implied claim instead of a checkable line.
Human edit: Human edit for Product Managers Write User Stories: rewrite the answer so each useful section names what came from the note, what still needs the actual notes, usable examples, boundary checks, and reviewer judgment, and where the person who will approve user stories should stop before sharing it; the editor also has to make each reusable section point back to the source note inside user stories; the edit has to preserve "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and leave story set with acceptance signals ready for a reviewer, not just prettier.
Reusable field: Reusable field for Product Managers Write User Stories: save the reusable fields as source note, audience, output shape, reviewer, stop rule, and job situation, user motivation, acceptance signal, and slice size; do not save private details or one-time facts as fixed wording. Keep the field set alert to this repeat risk: user stories can mention users without preserving job context and acceptance signals.

Questions before reuse

User Stories reader check: who will read or approve this user stories, and what do they already know?
User Stories source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
User Stories blank rule: what should stay blank or flagged if the actual notes, usable examples, boundary checks, and reviewer judgment is missing?

Who checks it

Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

User Stories source note: treat "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." as the factual base, not decorative background; the next usable asset is story set with acceptance signals.
User Stories evidence check: mark any section where the actual notes, usable examples, boundary checks, and reviewer judgment is assumed instead of shown, especially when user stories can mention users without preserving job context and acceptance signals.
User Stories scope check: keep the answer on job situation, user motivation, acceptance signal, and slice size; do not drift away from a product choice workflow where evidence and tradeoffs need to stay visible.
User Stories final polish: rewrite final wording only after user stories quality, job situation and user motivation, and ready-to-use evidence is clear enough for the product team, stakeholder, customer researcher, or release owner owner, then make each reusable section point back to the source note inside user stories.
User Stories freshness rule: For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

Usable output

A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.

Save this noteRough note that changes the prompt: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Task-specific source material: user segment, job, pain, desired outcome, and acceptance signals Human check to keep visible: user stories quality, job situation and user motivation, and ready-to-use evidence

Stop hereReject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Save for reuseReuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals 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

Product Managers bring user stories source notes: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The source says "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." The answer needs to become story set with acceptance signals 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 keep user value separate from solution details.

Why this input is messy

This user stories input needs care because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over the actual notes, usable examples, boundary checks, and reviewer judgment, miss job situation, user motivation, acceptance signal, and slice size, or make user stories look ready before the person approving user stories checks it, especially when user stories can mention users without preserving job context and acceptance signals.

First prompt move

product manager should start the user stories run by asking ChatGPT to ask ChatGPT to restate the source notes in three buckets before writing: facts it can use, assumptions it must not hide, and missing points that affect the actual notes, usable examples, boundary checks, and reviewer judgment; this is a context pass before polish because user stories with the usable answer first, then gaps and follow-up checks has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in user stories: who will read this user stories, and what do they already know?
Source detail in user stories: which note details are verified facts, and which parts still need the actual notes, usable examples, boundary checks, and reviewer judgment?
Constraint detail in user stories: what tone, length, channel, or approval rule matters before the answer reaches a product team, stakeholder, customer researcher, or release owner?
Reuse detail in user stories: which person will inspect user stories quality, job situation and user motivation, and ready-to-use evidence, and what would make the answer unsafe to reuse?

Usable answer shape

The user stories answer should return user stories with the usable answer first, then gaps and follow-up checks, separate source-backed sections from assumptions and open questions, show how job situation, user motivation, acceptance signal, and slice size shaped the result, name the person approving user stories, and end with a short check for user stories quality, job situation and user motivation, and ready-to-use evidence before the answer is shared or saved.

Human revision

product manager should revise the user stories answer by keeping the parts that saved review time, make each reusable section point back to the source note inside user stories, replace private or one-off details with reusable fields, and shape the closing version for a product team, stakeholder, customer researcher, or release owner; check it against "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep this final standard visible: the final stories should be testable, scoped, and traceable to user evidence.

Save or discard

Save the user stories run only when the note, output shape, checker, story set with acceptance signals, 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 actual notes, usable examples, boundary checks, and reviewer judgment is implied but not checkable.

Run prompt Grade answer Repair answer

Choose the right workflow for this job

Work moment

The page is for the moment when product managers have enough notes to create user stories, but still need a choice about job situation, user motivation, acceptance signal, and slice size.

Why this workflow

Do first

Next best workflow

ChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.

What to look for

Rough note that changes the prompt: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
Task-specific source material: user segment, job, pain, desired outcome, and acceptance signals
Human check to keep visible: user stories quality, job situation and user motivation, and ready-to-use evidence
Evidence pressure point: the actual notes, usable examples, boundary checks, and reviewer judgment

Wrong page if

The user cannot provide user segment, job, pain, desired outcome, and acceptance signals and would need ChatGPT to invent the important facts.
The desired result is not user stories or cannot be shaped as user stories with the usable answer first, then gaps and follow-up checks.
The task would be safer on ChatGPT Prompts for Product Managers 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 Write User Stories when your notes already include this check: Task-specific source material: user segment, job, pain, desired outcome, and acceptance signals.; 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 user segment, job, pain, desired outcome, and acceptance signals and would need ChatGPT to invent the important facts.
Define acceptance criteria: Use this workflow
Stay with ChatGPT Prompts for Product Managers to Write User Stories when your notes already include this check: Human check to keep visible: user stories quality, job situation and user motivation, and ready-to-use evidence.; Switch instead
Switch to Define acceptance criteria 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 user stories or cannot be shaped as user stories with the usable answer first, then gaps and follow-up checks.
Prioritize roadmaps: Use this workflow
Stay with ChatGPT Prompts for Product Managers to Write User Stories when your notes already include this check: Evidence pressure point: the actual notes, usable examples, boundary checks, 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 ChatGPT Prompts for Product Managers because the main choice is closer to that workflow.

Run the page by work state

Start by turning the rough request into named fields before asking for user stories.

Build The Asset

Use this when the notes are ready and the next useful output is user stories with the usable answer first, then gaps and follow-up checks, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for user stories with assumptions separated from source-backed details.
Bring: Bring the task focus: job situation, user motivation, acceptance signal, and slice size. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete user stories.
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 user segment, job, pain, desired outcome, and acceptance signals; add the reviewer, the audience, and the boundary from this case: The prompt must keep user value separate from solution details.

Reusable handoff

A usable handoff is user stories with the usable answer first, then gaps and follow-up checks with assumptions, source-backed sections, and a reviewer note for user stories quality, job situation and user motivation, and ready-to-use evidence.

Reality checks

Does the page-specific note "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." change the prompt, or could this still fit another task unchanged?
Can the reviewer check user stories quality, job situation and user motivation, and ready-to-use evidence without asking ChatGPT to invent missing facts?
Does the answer become user stories, or does it stay at broad user stories 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

Write user stories for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become user stories.

Use this when: Use before asking ChatGPT for user stories so the model has enough task-specific context.
When this fits: Turn user segment, job, pain, desired outcome, and acceptance signals into user stories for a product team, stakeholder, customer researcher, or release owner.
Do next: Compare the answer against the original notes and mark every line that depends on the actual notes, usable examples, boundary checks, and reviewer judgment.

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 Write User Stories

Goal: Find a copyable prompt workbench that helps product managers with user stories, using the right source material, review lens, example, and follow-up prompts.
Working scenario: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The user stories work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. For user stories work, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a product manager checks first.

What I know:
Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.

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 user stories. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

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 Write User Stories?
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 Write User Stories?
Who should check the answer before it is reused: Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.?

Output grader before reuse

0/5

Paste ChatGPT output

0 words checked against Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals and does not fill missing facts with confident guesses.Output shape, write user stories: the result clearly becomes user stories, not broad advice about the task.Handoff clarity, write user stories: the answer names missing inputs and the next human check for user stories quality, job situation and user motivation, and ready-to-use evidence.Audience fit, write user stories: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and choice context.Risk boundary, write user stories: the final version respects Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Needs another review pass

user stories final pass: keep the useful structure, then make each reusable section point back to the source note inside user stories; readiness means a product team, stakeholder, customer researcher, or release owner can see what was provided, what was assumed, why user stories can mention users without preserving job context and acceptance signals, and what still needs review.

Task-specific output diagnosis

Paste the first Write User Stories answer and compare it with "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." before checking style. A useful product manager output must prove it belongs to this page by keeping job situation, user motivation, acceptance signal, and slice size, user stories with the usable answer first, then gaps and follow-up checks, and the task reviewer visible.

Pass when

The answer uses "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." as the controlling case, not as decoration, and turns it into user stories with the usable answer first, then gaps and follow-up checks with job situation, user motivation, acceptance signal, and slice size still visible.
The answer shows which lines come from "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the user stories.
The answer gives the task reviewer a clear check tied to "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", especially the point where the actual notes, usable examples, boundary checks, and reviewer judgment cannot be treated as proven.
The answer can become user stories prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.", so the write user stories output could fit another page.
It gives a generic next step while hiding job situation, user motivation, acceptance signal, and slice size, which makes the answer feel useful before it can support the real user stories.
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 user stories with the usable answer first, then gaps and follow-up checks, the actual notes, usable examples, boundary checks, and reviewer judgment, or the source material that makes this write user stories page different.

Repair next

Rewrite the opening around "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep the first sentence tied to job situation, user motivation, acceptance signal, and slice size before improving tone or length.
Add a needs-checking block for the actual notes, usable examples, boundary checks, and reviewer judgment, then separate supplied facts from assumptions before returning user stories with the usable answer first, then gaps and follow-up checks.
Mark the line the task reviewer must inspect for user stories quality, job situation and user motivation, and ready-to-use evidence, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved user stories prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the write user stories check.

Red flags

Evidence issue, write user stories: the answer invents or overstates the actual notes, usable examples, boundary checks, and reviewer judgment.
Task drift, write user stories: it ignores job situation, user motivation, acceptance signal, and slice size and moves into a neighboring workflow.
Readiness gap, write user stories: it sounds complete while leaving user stories quality, job situation and user motivation, and ready-to-use evidence impossible to verify.
Privacy issue, write user stories: it includes details that should have been summarized or removed.
Generic output, write user stories: 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep the first sentence tied to job situation, user motivation, acceptance signal, and slice size before improving tone or length.
Add a needs-checking block for the actual notes, usable examples, boundary checks, and reviewer judgment, then separate supplied facts from assumptions before returning user stories with the usable answer first, then gaps and follow-up checks.

Repair pass

Output next pass for: Write User Stories: review user stories
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 user stories, using the right source material, review lens, example, and follow-up prompts.

Repair moves:
- Rewrite the opening around "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and keep the first sentence tied to job situation, user motivation, acceptance signal, and slice size before improving tone or length.
- Add a needs-checking block for the actual notes, usable examples, boundary checks, and reviewer judgment, then separate supplied facts from assumptions before returning user stories with the usable answer first, then gaps and follow-up checks.
- Mark the line the task reviewer must inspect for user stories quality, job situation and user motivation, and ready-to-use evidence, and move unsupported claims out of the usable answer.
- Replace one-time details with variables for the saved user stories prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the write user stories check.

Keep if repaired:
- The answer uses "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." as the controlling case, not as decoration, and turns it into user stories with the usable answer first, then gaps and follow-up checks with job situation, user motivation, acceptance signal, and slice size still visible.
- The answer shows which lines come from "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the user stories.

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

A rushed Product Managers Write User Stories pass copies a line like "Here is a polished version based on your notes It covers the main points, keeps a professional tone, and adds a useful next step" and then moves on. Write User Stories failure to avoid for product manager: it also leaves no place for assumptions, missing facts, or a reviewer note; the actual note to protect is Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.

Why it fails

Write User Stories repair note: the answer looks confident because it uses smooth wording, but it never proves where the key claims came from Restore job situation, user motivation, acceptance signal, and slice size at the top of the second pass; label the lines that rely on the actual notes, usable examples, boundary checks, and reviewer judgment, name the person approving user stories before sharing with a product team, stakeholder, customer researcher, or release owner, and solve the practical snag: user stories can mention users without preserving job context and acceptance signals.

Trace the rough note

Problem: The answer mentions user stories but does not reflect the concrete case: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where story set with acceptance signals changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking user stories quality, job situation and user motivation, and ready-to-use evidence.
Repair: Add a reviewer line for the person approving user stories, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply the actual notes, usable examples, boundary checks, 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 write user stories into broad advice that does not produce user stories with the usable answer first, then gaps and follow-up checks.
Repair: Force the final answer back into user stories with the usable answer first, then gaps and follow-up checks, keep job situation, user motivation, acceptance signal, and slice size as the main choice point, and make each reusable section point back to the source note inside user stories.

Human-edited direction

Human Write User Stories revision for Product Managers: start with the actual case, name the audience, return user stories with the usable answer first, then gaps and follow-up checks, keep supplied notes, assumptions, and missing checks separate, then make each reusable section point back to the source note inside user stories, tell a product team, stakeholder, customer researcher, or release owner what is ready to use, what the person approving user stories must verify, and how the answer becomes user stories prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun Product Managers Write User Stories: repair this write user stories answer, keep the result focused on job situation, user motivation, acceptance signal, and slice size, return user stories with the usable answer first, then gaps and follow-up checks, put unsupported claims about the actual notes, usable examples, boundary checks, and reviewer judgment in a needs-checking block, name the reviewer as the person approving user stories, protect this boundary "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.", and use only these source notes: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.

Accept when

The answer visibly uses the rough note instead of generic write user stories advice.
The result is shaped as user stories with the usable answer first, then gaps and follow-up checks and can be checked by the person approving user stories.
Any uncertain point about the actual notes, usable examples, boundary checks, and reviewer judgment is separated from the usable parts.
The reusable version keeps job situation, user motivation, acceptance signal, and slice size 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 user stories quality, job situation and user motivation, 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

Product managers need user story prompts that connect user job, context, and acceptance signals. This page is for product managers user stories work when user stories can mention users without preserving job context and acceptance signals. Search edge for user stories with product managers: show story set with acceptance signals, a human review path for user stories, and the task-specific reason the page deserves the query. Outside support for user stories with product managers: an independent resource must mention the user stories page visibly before story set with acceptance signals becomes an authority claim. User stories work for product manager needs its own page because a useful visit starts when the prompt reflects user segment, job, pain, desired outcome, and acceptance signals, the actual story set with acceptance signals, and the review choice that follows the answer.

Concrete scenario

A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The user stories work happens inside a product choice workflow where evidence and tradeoffs need to stay visible. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. For user stories work, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a product manager checks first.

Real user input

Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Phrase shopping fails for user stories work because the note should become story set with acceptance signals. The next version should keep that rough note visible. This user stories work run should turn that note into user stories. For user stories work, paste the source as bullets, constraints, and audience notes so the model has enough shape for user stories with the usable answer first, then gaps and follow-up checks.

Editor take

The prompt must keep user value separate from solution details. In this user stories review, the edit is to make each reusable section point back to the source note inside user stories. Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch. In the user stories work review, the editor should reward prompts that make the actual notes, usable examples, boundary checks, and reviewer judgment visible and penalize answers that hide missing context behind fluent wording; compare the answer with the actual notes before reuse.

Human polish

The final stories should be testable, scoped, and traceable to user evidence. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible. Before handing off the user stories, the final human edit should keep the useful structure, remove unsupported details, add verified context, and check user stories quality, job situation and user motivation, and ready-to-use evidence before the output reaches a product team, stakeholder, customer researcher, or release owner. Keep a short record of what changed before reuse. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

Fast use path

Main card for user stories: copy the recommended prompt first, not every variation.
Source material for user stories: replace [source_material] with user segment, job, pain, desired outcome, and acceptance signals.
Audience details for user stories: add the real audience and the constraint that matters most for user story writing.
Review pass for user stories: run the review prompt against user stories quality, job situation and user motivation, and ready-to-use evidence before using the answer.

Specificity signals

A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects.
Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
user segment, job, pain, desired outcome, and acceptance signals
job situation, user motivation, acceptance signal, and slice size
the actual notes, usable examples, boundary checks, and reviewer judgment
Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
story set with acceptance signals
user stories can mention users without preserving job context and acceptance signals
make each reusable section point back to the source note inside user stories
a product choice workflow where evidence and tradeoffs need to stay visible
For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.
Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.
Search edge for user stories with product managers: show story set with acceptance signals, a human review path for user stories, and the task-specific reason the page deserves the query.
Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.
Outside support for user stories with product managers: an independent resource must mention the user stories page visibly before story set with acceptance signals becomes an authority claim.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

User Stories reader check: who will read or approve this user stories, and what do they already know?
User Stories source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
User Stories blank rule: what should stay blank or flagged if the actual notes, usable examples, boundary checks, and reviewer judgment is missing?
User Stories stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

User Stories source note: treat "Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out." as the factual base, not decorative background; the next usable asset is story set with acceptance signals.
User Stories evidence check: mark any section where the actual notes, usable examples, boundary checks, and reviewer judgment is assumed instead of shown, especially when user stories can mention users without preserving job context and acceptance signals.
User Stories scope check: keep the answer on job situation, user motivation, acceptance signal, and slice size; do not drift away from a product choice workflow where evidence and tradeoffs need to stay visible.
User Stories final polish: rewrite final wording only after user stories quality, job situation and user motivation, and ready-to-use evidence is clear enough for the product team, stakeholder, customer researcher, or release owner owner, then make each reusable section point back to the source note inside user stories.
User Stories freshness rule: For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.
User Stories failure pattern: Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.
User Stories choice owner: Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.

Before and after

Weak answer risk: The weak user stories answer risk is specific: the answer sounds complete while turning "need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions; keep implementation out;" into broad advice, hiding missing context around the actual notes, usable examples, boundary checks, and reviewer judgment, and leaving a product team, stakeholder, customer researcher, or release owner without a clear choice path because user stories can mention users without preserving job context and acceptance signals. Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.
Improved outcome: A usable user stories handoff would return user stories with named sections, action bullets, and a final reviewer pass; split the user's pasted facts from anything ChatGPT inferred, put the reviewer beside the section they must approve, prepare story set with acceptance signals, and center the last read on user stories quality, job situation and user motivation, and ready-to-use evidence.
Why it feels real: The user stories example feels grounded because: 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 user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.

When to save this version

Reuse user stories only after private details are removed, one-time facts become variables, make each reusable section point back to the source note inside user stories, and the review rule for job situation, user motivation, acceptance signal, and slice size still appears in the reusable prompt. Approval for product managers user stories belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the story set with acceptance signals review standard visible.

The job this page helps finish

Searchers arrive with user segment, job, pain, desired outcome, and acceptance signals already in hand and need help turning it into user stories. The page has to show the source fields, the output shape, and the point where a product team, stakeholder, customer researcher, or release owner should stop and review. The distinct task pressure is job situation, user motivation, acceptance signal, and slice size.

Use Cases

Turn user segment, job, pain, desired outcome, and acceptance signals into user stories for a product team, stakeholder, customer researcher, or release owner.
Review an existing user stories answer for user stories checkpoint, missing details, and unsupported claims.
Create a repeatable user stories prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make job situation, user motivation, acceptance signal, and slice size visible so the answer stays tied to user stories instead of drifting into a neighboring task.
Condense a long ChatGPT answer into user stories with the usable answer first, then gaps and follow-up checks 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 user segment, job, pain, desired outcome, and acceptance signals; do not ask the model to guess it.
Name the final choice the user stories 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 actual notes, usable examples, boundary checks, and reviewer judgment.
Add the task-specific focus: job situation, user motivation, acceptance signal, and slice size.

Check the answer against real references

What users are trying to finish

Searchers who land on user stories want a prompt they can run against real material, usually user segment, job, pain, desired outcome, and acceptance signals. They should leave knowing which fields to replace, which claims need review, and why job situation, user motivation, acceptance signal, and slice size changes the answer. This page has to connect user segment, job, pain, desired outcome, and acceptance signals to user stories, show user stories with the usable answer first, then gaps and follow-up checks, and leave user stories quality, job situation and user motivation, and ready-to-use evidence with a named human reviewer.

Why the workflow matters

The page earns its place by pairing the recommended prompt with a filled case, a reject-if rule, and a repair prompt tied to job situation, user motivation, acceptance signal, and slice size. That gives the page a clearer job than a list of examples: it helps the user decide whether the answer is ready.

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 actual notes, usable examples, boundary checks, 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 user stories.
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 user stories needs human oversight, assumptions, and review controls.
FTC advertising and marketing guidanceUsed as the second product reference when user stories affects market-facing claims, support language, or customer communication.

Related ways people ask for this task

Question covered: chatgpt prompts for product managers user stories

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

user stories chatgpt prompt for product managers
best chatgpt prompts for user stories
user stories prompt template for product managers
copyable user stories chatgpt prompt
user stories ai prompt with review checklist
chatgpt user stories 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 user stories and not just a blank prompt.
Look for missing-source risks around the actual notes, usable examples, boundary checks, 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 user stories", this page should win only if the reader can turn user segment, job, pain, desired outcome, and acceptance signals into user stories with the usable answer first, then gaps and follow-up checks and still know who checks user stories.

Compare against

A broad product managers prompt collection that gives short examples without a worked story set with acceptance signals.
A role guide that explains product managers work but does not turn user segment, job, pain, desired outcome, and acceptance signals into user stories with the usable answer first, then gaps and follow-up checks.
A prompt generator page that creates wording but leaves the user stories check to the user.
A task article that teaches write user stories but does not give a copyable run with a check step.

This page is stronger when

It starts from user segment, job, pain, desired outcome, and acceptance signals, then shapes the answer into user stories with the usable answer first, then gaps and follow-up checks instead of asking the reader to invent context.
It keeps the user stories check visible, so a smooth answer is not treated as ready before a person checks it.
It shows a weak-answer repair path for user stories can mention users without preserving job context and acceptance signals, 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 actual notes, usable examples, boundary checks, 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 user stories" and this page does not yet answer that wording.
Readers cannot see story set with acceptance signals 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 user stories.

Check the answer before you reuse it

Who checks it

Use the review lane to test whether the answer is specific enough for user stories with the usable answer first, then gaps and follow-up checks and safe enough for reuse.

Real-world case

user stories scenario: the page earns trust when the reviewer can see whether product managers provide user segment, job, pain, desired outcome, and acceptance signals, need user stories with the usable answer first, then gaps and follow-up checks, and must keep job situation, user motivation, acceptance signal, and slice size visible while checking the actual notes, usable examples, boundary checks, and reviewer judgment. For product managers, write user stories is reviewed inside a product choice workflow where evidence and tradeoffs need to stay visible, with story set with acceptance signals as the concrete item on the desk.

Checks before sharing

Source review, write user stories: the answer uses the supplied user segment, job, pain, desired outcome, and acceptance signals and does not fill missing facts with confident guesses.
Output shape, write user stories: the result clearly becomes user stories, not broad advice about the task.
Handoff clarity, write user stories: the answer names missing inputs and the next human check for user stories quality, job situation and user motivation, and ready-to-use evidence.
Audience fit, write user stories: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and choice context.
Risk boundary, write user stories: 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 user stories

Result user stories product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Example user stories product managers check: compare whether competing pages show a filled example for user stories using realistic user segment, job, pain, desired outcome, and acceptance signals.
Evidence user stories product managers check: mark whether each page explains how to verify the actual notes, usable examples, boundary checks, and reviewer judgment and user stories quality, job situation and user motivation, and ready-to-use evidence.
Differentiator user stories product managers check: compare the top results against this page promise: Search edge for user stories with product managers: show story set with acceptance signals, a human review path for user stories, and the task-specific reason the page deserves the query.
Failure user stories product managers check: mark whether competing pages show this failure mode or avoid it: Failure pattern for user stories with product managers: the user stories can sound polished while user stories can mention users without preserving job context and acceptance signals, so the page should make that miss easy to catch.
Freshness user stories product managers check: record whether competing pages say how source notes stay current. For product managers user stories, current source notes should come first; stale or partial inputs should trigger a fresh story set with acceptance signals pass instead of another saved answer.
Page type user stories product managers check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ user stories 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 user stories with product managers: an independent resource must mention the user stories page visibly before story set with acceptance signals 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 write user stories 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 write user stories by turning [source_material] into user stories for [audience]. Keep the task focus on job situation, user motivation, acceptance signal, and slice size. Use this output shape: user stories with the usable answer first, then gaps and follow-up checks. Do not add facts beyond the source. End with a review checklist for user stories quality, job situation and user motivation, and ready-to-use evidence and the actual notes, usable examples, boundary checks, 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 is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. The user needs help with user stories, but the real job is to turn a messy request into user stories that a product team, stakeholder, customer researcher, or release owner can review without hidden assumptions.

Weak prompt

Write a good user stories from this: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.

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 job situation, user motivation, acceptance signal, and slice size, inventing details, or skipping user stories quality, job situation and user motivation, and ready-to-use evidence.

Stronger prompt

Act as a careful assistant for Product Managers.
I need help with user stories. Use only this source material: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
The usual source material for this task is user segment, job, pain, desired outcome, and acceptance signals.
The audience is [audience], and the output must work for a product team, stakeholder, customer researcher, or release owner.
Create user stories in this shape: user stories with the usable answer first, then gaps and follow-up checks.
Keep the task focus on job situation, user motivation, acceptance signal, and slice size.
Respect this editorial rule: The prompt must keep user value separate from solution details.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for user stories quality, job situation and user motivation, and ready-to-use evidence, the actual notes, usable examples, boundary checks, 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 actual notes, usable examples, boundary checks, and reviewer judgment visible for human checking.

Sample input

A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. User notes: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out. Audience: a product team, stakeholder, customer researcher, or release owner. Constraints: avoid unsupported claims, protect private details, and keep focus on job situation, user motivation, acceptance signal, and slice size.

Example answer shape

A useful answer starts by restating the real situation, then provides user stories with the usable answer first, then gaps and follow-up checks. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for user stories quality, job situation and user motivation, and ready-to-use evidence, the actual notes, usable examples, boundary checks, 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 stories should be testable, scoped, and traceable to user evidence.

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 user stories 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 job situation, user motivation, acceptance signal, and slice size is still the center of the answer. The pass is accepted only when the final stories should be testable, scoped, and traceable to user evidence.

Fit

Use when product managers have real source notes for user stories.
Use when the desired result is user stories, not broad advice.
Use when a human can review user stories quality, job situation and user motivation, 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 actual notes, usable examples, boundary checks, 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: Write user stories example from rough notes

Example input

A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects. Raw input: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.

Prompt use

Use the evidence-aware prompt to convert those notes into user stories, then run the review prompt against this editorial rule: The prompt must keep user value separate from solution details.

What the answer should look like

A useful answer would return user stories with the usable answer first, then gaps and follow-up checks 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 job situation, user motivation, acceptance signal, and slice size at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially the actual notes, usable examples, boundary checks, and reviewer judgment. The human pass is not decoration here: The final stories should be testable, scoped, and traceable to user evidence.

Review notes

Confirm the answer reflects this actual situation: A PM is writing stories for saved prompt collections after interviews showed users reuse prompts across client projects.
Compare the output against the raw user input: Need stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out.
Confirm the source material really supports the actual notes, usable examples, boundary checks, and reviewer judgment.
Check that the wording fits a product team, stakeholder, customer researcher, or release owner.
Confirm the answer handles job situation, user motivation, acceptance signal, and slice size 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 user stories. Target result: user stories.
Source material I can provide: user segment, job, pain, desired outcome, and acceptance signals. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size. If the pasted focus is broad, compare it with this page cue: job situation, user motivation, acceptance signal, and slice size.
Goal: make user stories 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 actual notes, usable examples, boundary checks, and reviewer judgment tied to user segment, job, pain, desired outcome, and acceptance signals, and mark any detail the notes do not support.
Run mode for user stories: 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 user stories with the usable answer first, then gaps and follow-up checks.
Before writing user stories, ask up to 3 clarifying questions when user segment, job, pain, desired outcome, and acceptance signals does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on user stories quality, job situation and user motivation, and ready-to-use evidence. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a working version they can inspect against the supplied notes.

beginner

Write user stories for product manager Context Intake Prompt

Use this before user stories 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, 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 user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, and ready-to-use evidence.

Follow-up prompt

Now improve this working version into user stories by tightening user stories quality, job situation and user motivation, and ready-to-use evidence, emphasizing job situation, user motivation, acceptance signal, and slice size, 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 actual notes, usable examples, boundary checks, and reviewer judgment, fits a product team, stakeholder, customer researcher, or release owner, reflects job situation, user motivation, acceptance signal, and slice size, and respects this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

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

advanced

Write user stories for product manager Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become user stories.

[source_material]: Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

Expected output

Expect user stories with the usable answer first, then gaps and follow-up checks that explicitly separates source-based content from assumptions and ends with a review pass for user stories quality, job situation and user motivation, and ready-to-use evidence.

Follow-up prompt

Human review

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

workflow

Write user stories for product manager Repeatable Workflow Prompt

Use this when user stories repeats often enough to become user stories 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, 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 user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, and ready-to-use evidence.

Follow-up prompt

Human review

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

review

Write user stories for product manager Human Review Prompt

Use this after there is already working copy and the main need is user stories quality, job situation and user motivation, 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a choice about accept, repair, or reject before polishing the wording.

[source_material]: Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, 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 user stories quality, job situation and user motivation, and ready-to-use evidence.

format

Write user stories 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a reshaped version plus a note showing what stayed unchanged.

[source_material]: Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, 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

Write user stories 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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a safe summary, removed-detail list, and a reusable version without sensitive data.

[source_material]: Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, 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

Write user stories for product manager Fast Checklist Prompt

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

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 user stories. Target result: user stories.
Source material I can provide: [source_material]. Typical source for this task is user segment, job, pain, desired outcome, and acceptance signals.
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: job situation, user motivation, acceptance signal, and slice size.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the actual notes, usable examples, boundary checks, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for user stories: 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 user stories, ask up to 3 clarifying questions when [source_material] does not include user segment, job, pain, desired outcome, and acceptance.
After the answer, include a human review section focused on [review_lens]. Verify the actual notes, usable examples, boundary checks, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: for user stories, The user should get a narrow next step they can complete before opening a longer prompt.

[source_material]: Paste the concrete product manager user stories notes, such as user segment, job, pain, desired outcome, and acceptance signals.Example: user segment, job, pain, desired outcome, and acceptance signals
[audience]: Who will read, use, approve, or act on this product manager user stories.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The choice or work outcome this product manager user stories run should support.Example: make user stories easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules for product manager user stories: tone, length, channel, privacy, and the actual notes, usable examples, boundary checks.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: Use this check before sharing: user stories quality, job situation and user motivation, and ready-to-use support.Example: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: The detail that keeps this product manager user stories prompt specific: job situation, user motivation, acceptance signal, and slice size.Example: job situation, user motivation, acceptance signal, and slice size

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 user stories quality, job situation and user motivation, 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]: user segment, job, pain, desired outcome, and acceptance signals
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make user stories 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]: user stories quality, job situation and user motivation, and ready-to-use evidence
[task_focus]: job situation, user motivation, acceptance signal, and slice size

Answer checks

Context: Does the prompt give enough user segment, job, pain, desired outcome, and acceptance signals to avoid guessing?
Specificity: Does the answer produce user stories rather than broad advice?
Task focus: Does it handle job situation, user motivation, acceptance signal, and slice size instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check user stories checkpoint and the actual notes, usable examples, boundary checks, 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 write user stories without giving user segment, job, pain, desired outcome, and acceptance signals.
Accepting polished wording before checking the actual notes, usable examples, boundary checks, 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: job situation, user motivation, acceptance signal, and slice size.
Skipping the review pass for user stories quality, job situation and user motivation, 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 user stories.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that job situation, user motivation, acceptance signal, and slice size is supported by the source material and not invented.
Have a human review user stories 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 write user stories?

Use a prompt that names user segment, job, pain, desired outcome, and acceptance signals, asks for user stories with the usable answer first, then gaps and follow-up checks, and ends with a review pass for user stories quality, job situation and user motivation, 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 user segment, job, pain, desired outcome, and acceptance signals.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against the actual notes, usable examples, boundary checks, 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: user stories quality, job situation and user motivation, 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.
Define acceptance criteriaUseful 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.

Write User Stories: review user stories

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

Write user stories 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 stories by user type, job-to-be-done, acceptance criteria, edge cases, and open questions. Keep implementation out" as the visible source line for user stories

any confident claim about the actual notes, usable examples, boundary checks, 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 job situation, user motivation, acceptance signal, and slice size 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: Write User Stories 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

Supplied context that should stay visible

Unverified points to keep separate

Stop rules for the first pass

Information that should not become a template

Fields to preserve across future use

Iteration loop: run the prompt as a working thread

Thread goal

First run

Gap fill

Skeptic pass

Handoff

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