Write User Stories for a Payments Feature
Turns a short description into a concrete plan to write user stories for a payments feature, with assumptions called out instead of silently guessed.
When to use this
Use before committing time to write user stories for a payments feature by hand, to get a first structured pass to react to.
Prompt template
Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.
Task: Write user stories for a payments feature.
Context to use:
- Feature or initiative: {{feature_or_initiative}}
- Key stakeholders: {{stakeholders}}
- Constraints or deadline: {{constraints}}
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistCustomize
Feature or initiative is required
Preview
Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.
Task: Write user stories for a payments feature.
Context to use:
- Feature or initiative: {{feature_or_initiative}} missing
- Key stakeholders:
- Constraints or deadline:
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistUsage instructions
Provide as much real context as you have; leave a field blank only if it genuinely doesn't apply, and check the assumptions list afterward.
Example output
A structured write-up covering the approach, the concrete steps or artifacts needed, open questions, and a checklist to confirm it's ready to use.
Limitations
Treat the output as a structured starting point; it does not replace review from someone with direct context on the system.
Rate this prompt
Not yet rated