Reusable frameworks

17 User Story Templates

Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.

Use the framework

How to personalize a template

A strong user story describes one valuable user outcome without prematurely prescribing the interface or technical implementation. It is small enough to discuss and estimate in the team’s workflow, gives enough context to understand the value, and can be paired with acceptance criteria that make completion testable.

  1. 1
    Choose the template closest to your actual purpose.
  2. 2
    Replace every bracketed field with specific information.
  3. 3
    Delete any sentence that does not belong in your situation.
  4. 4
    Read the result aloud for unnatural transitions or repeated phrasing.
  5. 5
    Verify names, dates, links, facts, and promises before sending or publishing.
User Story Template 1
Basic user story
As a [specific role], I want [goal/capability] so that [user value].
User Story Template 2
Story + acceptance criteria
Story: As a [role], I want [goal] so that [reason].
Acceptance criteria:
- [observable condition]
- [boundary/error condition]
- [completion condition]
User Story Template 3
Problem → story
Observed user problem: [x]
Affected role: [x]
Desired outcome: [x]
Implementation assumptions removed: [x]
Final story: [x]
User Story Template 4
Story splitting
Oversized story: [x]
Independent outcome A: [x]
Independent outcome B: [x]
Dependency if any: [x]
User Story Template 5
INVEST-style review
Independent enough? [ ]
Negotiable? [ ]
Valuable? [ ]
Estimable enough for this workflow? [ ]
Small enough? [ ]
Testable? [ ]
User Story Template 6
Failure-mode and reader-intent audit for User Story: visible symptom → [ ]; likely underlying problem → [ ]; reader need → [ ]; competing technique considered → [ ]; correction → [ ]; evidence/genre/format constraint → [ ]; final verification → [ ].
User Story Template 7
Boundary-and-tool-choice audit for User Story: reader objection → [ ]; actual writing job → [ ]; evidence/genre/format boundary → [ ]; tempting alternative → [ ]; why it is the wrong tool here → [ ]; correct adjustment → [ ]; final verification → [ ].
User Story Template 8
Evidence/support and mastery ladder for User Story: minimum acceptable → [ ]; strong → [ ]; expert → [ ]; audience/genre constraint → [ ]; evidence or story support → [ ]; boundary that would require a different technique → [ ].
User Story Template 9
Certainty and expert-exception audit for User Story: statement or choice → [ ]; evidence/canon/authority supporting it → [ ]; confidence level → [ ]; uncertainty that must be named → [ ]; expert exception → [ ]; nearest alternative technique → [ ]; why the final choice fits better → [ ].
User Story Template 10
Purpose-and-verification decision audit for User Story: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
User Story Template 11
Publication-readiness audit for User Story: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
User Story Template 12
Provenance and classification audit for User Story: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
User Story Template 13
Source-record and update audit for User Story: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
User Story Template 14
Source-ledger and revision-history audit for User Story: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
User Story Template 15
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
User Story Template 16
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
User Story Template 17
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].