SaaS User Story Criteria Writer
By General Input
Help a B2B SaaS product owner bring one admin or user workflow story to backlog refinement. Translate supplied agreed behavior into observable Given/When/Then criteria and surface permission or product decisions needed before the story can be agreed.
Industries
Capabilities
- Source-backed Given/When/Then criteria for one SaaS admin or user workflow story.
- A separate list of unresolved permission and product decisions for refinement.
- Every supplied requirement covered or explicitly unresolved, without inventing behavior.
Included resources
SaaS User Story Criteria Writer Method
Draft SaaS User Story Criteria
What to bring
- One B2B SaaS admin or user workflow story and its intended outcome.
- Requirement notes for that story, each with a unique ID.
- Optional role terminology, scope exclusions, and confirmed constraints.
Setup
- Add the specialist and let it review its skill and workflow.
- Ask which SaaS role terminology, Given/When/Then conventions, and scope exclusions the product owner uses in backlog refinement. No outside account connection is needed.
- Enable the on-demand workflow and supply current-run material, or try the fictional sample.
Scope
- Prepare acceptance criteria for one B2B SaaS admin or user workflow story entering backlog refinement. Do not split a broad feature into stories, write implementation tasks, or choose undecided permissions, defaults, or limits.
- Stop at draft story criteria and product-owner decisions needed. Do not make product decisions, expand scope, prioritize the backlog, or update tickets. Do not invent permissions, limits, error text, success thresholds, or defaults.
Example
Fictional input and an illustrative result.
Input
Fictional SaaS story for refinement: a report owner wants to rename a saved report. R1 says the new name appears in the owner’s list. R2 leaves shared-report rename permissions undecided.
Output
AC1 — draft for refinement
Given a user owns a saved report, when they rename it, then their saved-report list shows the new name. Source: R1.
Product-owner decision needed
R2: Who may rename a shared report? No permission rule has been assumed and no ticket has been updated.