User Story Template 1
Basic user story As a [specific role], I want [goal/capability] so that [user value].
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.
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.
Basic user story As a [specific role], I want [goal/capability] so that [user value].
Story + acceptance criteria Story: As a [role], I want [goal] so that [reason]. Acceptance criteria: - [observable condition] - [boundary/error condition] - [completion condition]
Problem → story Observed user problem: [x] Affected role: [x] Desired outcome: [x] Implementation assumptions removed: [x] Final story: [x]
Story splitting Oversized story: [x] Independent outcome A: [x] Independent outcome B: [x] Dependency if any: [x]
INVEST-style review Independent enough? [ ] Negotiable? [ ] Valuable? [ ] Estimable enough for this workflow? [ ] Small enough? [ ] Testable? [ ]
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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 → [ ].
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].
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].
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 → [ ].