Skip to contentComing soon: SprintProof for ChatGPT and Codex

Free template

User story template

One story, written so a developer can build it and a tester can check it: who wants what and why, the context, the criteria for done, the edge cases, what is left out and a range for the effort. Each section says what to write and what reviewers push back on.

Markdown pastes into Jira, Linear, Notion and GitHub issues. No sign-up.

The template

Eight parts of a story, each with what to write.

A story is a promise to hold a conversation, not a spec. Write it so that conversation starts from facts. A good story is independent, negotiable, valuable, estimable, small and testable (INVEST); each part below helps with one of those.

user-story-template.md
blank, with guidance
  1. 01

    Story

    One sentence: “As a [role], I want [action], so that [outcome].”

    • Which role, named as precisely as the product names it?
    • What does that person do, in their words rather than the system’s?
    • What do they get that they could not get before?

    TipThe most common failure is a “so that” that restates the want: “I want to see a list, so that I can see the list.” Ask what the person does next with it.

  2. 02

    Context

    The background a developer needs and the story itself leaves out.

    • What happens today, and what hurts?
    • Where in the product does this live?
    • Which story or plan is it part of?

    TipTwo or three sentences. If you need more, the story is probably several stories.

  3. 03

    Acceptance criteria

    The checks that make the story done. A tester should be able to answer yes or no to each.

    • What is the happy path, step by step?
    • Which rules and limits apply: roles, rate limits, expiry?
    • What does the user see when it fails?

    TipCap it at five to seven. More than that and the story is not small. Use the acceptance criteria template for the detailed format.

  4. 04

    Edge cases and states

    The situations beyond the happy path that the story must still handle.

    • What if the input already exists, is empty or is wrong?
    • Which states does the screen need: empty, loading, error, no access?
    • What if the user is on the wrong account or has lost access?

    TipEach edge case becomes a criterion, an open question or an item under out of scope. None should stay unsaid.

  5. 05

    Out of scope

    What this story deliberately does not cover, so the next one can.

    • What would a reviewer assume is included?
    • Which part is a separate story?
    • What did you cut to keep the story small?

    TipA story that is a task in disguise (“add a column to the invitations table”) has no user and no outcome. Write it as a task under the story instead.

  6. 06

    Open questions

    What you do not know yet, each with an owner and a date to decide by.

    • Which decision belongs to another team?
    • What answer would change the size of the story?
    • Who decides, and by when?

    TipA story with an unanswered question is not ready for a sprint. Either answer it or split it off.

  7. 07

    Estimate

    A range for the whole story, so the team sees how far the bad case is from the likely one.

    • Best, likely and worst case, in days
    • What makes the worst case worse?
    • Is it still small enough to finish in one sprint at the worst case?

    TipNever one number. If the worst case does not fit in a sprint, split the story before planning.

  8. 08

    Links

    Where the design, the parent plan and the discussion live.

    • The design file or screen
    • The parent plan or PRD
    • Related stories and the tasks built from this one

    TipLink, do not paste. A copied design goes stale the day it is copied.

Example

Three user stories from team invitations, filled in.

Stories taken from the Team invitations plan that SprintProof’s sample workspace uses: an admin invites people, an invitee opens the link on the wrong account, and an admin revokes an invite.

team-invitations-stories.md
example, filled in
INV · USER STORIES · OWNER MARIA K.Team invitations: three stories

1 · Story S1

As a workspace admin, I want invite several colleagues by email and pick a role for them, so that they can start work today without asking us to add each person by hand.

2 · Context

Today an admin has to ask us to add every person. The invite modal is where all invitations start, so the role rules and the send limit show up here first.

3 · Acceptance criteria

  • The email field accepts one address or many pasted at once, separated by commas, spaces or new lines.
  • The role picker offers only roles the admin may grant: admins can invite admins and members.
  • A bad address shows an error next to it; the valid ones are still sent.
  • The 21st invite in an hour returns 429 with the time to try again, and the modal explains the limit.

4 · Edge cases and states

  • A pending invite already exists for the address: the existing one is returned, not a second row.
  • The address already has an account: open question below.

5 · Out of scope

  • CSV import: pasting many addresses covers it for now
  • Domain auto-join: needs verified domains first

6 · Open questions

What if the invited email already has an account?Jonas T. · Tue

7 · Estimate

BestLikelyWorst
2.5 d3.5 d7 d

Sum of: Invite modal, Permission rules, Rate limit invite sends.

8 · Links

  • Design: Invite modal and accept page, in the design file
  • Parent plan: Team invitations (INV)
  • Tasks: INV-5, INV-8, INV-11

1 · Story S2

As a invitee, I want switch accounts when I open an invite while signed in as someone else, so that I join the right workspace with the address I was invited at, without losing the link.

2 · Context

People open invite links on a laptop where they are already signed in with a personal or other work account. The page must tell them, not fail.

3 · Acceptance criteria

  • Signed in as a different account, the page says the invite was sent to another address and offers “Switch account”.
  • Switching keeps the invite link alive through login, and the invitee lands in the invited workspace.
  • The same link works once: a used or revoked link shows its own message.
  • The page works at 375 px width and with a screen reader.

4 · Edge cases and states

  • Signed out: the page offers sign-in or sign-up for the invited address.
  • Expired link (after 7 days): the page says so and tells the invitee to ask an admin for a new one.

5 · Out of scope

  • Letting anyone with the link join: only the invited address can accept

6 · Open questions

Can anyone with the link join, or only the invited address?Jonas T. · Tue

7 · Estimate

BestLikelyWorst
2 d3 d6 d

Sum of: Accept-invite page, Invite tokens.

8 · Links

  • Design: Invite modal and accept page, in the design file
  • Parent plan: Team invitations (INV)
  • Tasks: INV-2, INV-10

1 · Story S3

As a workspace admin, I want revoke an invite that has not been accepted, so that a link sent to the wrong person stops working before they can use it.

2 · Context

Invites are links that grant access. When one goes to the wrong address, the admin needs to kill it from the pending list.

3 · Acceptance criteria

  • The pending list shows email, role, invited by and age, with resend and revoke on each row.
  • Revoke asks for confirmation and updates the list without a reload.
  • A revoked token is rejected on its next use.
  • Empty, loading and error states are designed and reachable by keyboard.

4 · Edge cases and states

  • Revoking an invite that was accepted a moment ago: the row shows the invite as accepted and no revoke is offered.

5 · Out of scope

  • Bulk revoke: one row at a time for now

6 · Open questions

None. Ready for a sprint.

7 · Estimate

BestLikelyWorst
1 d2 d3 d

Sum of: Pending invites list.

8 · Links

  • Design: Invite modal and accept page, in the design file
  • Parent plan: Team invitations (INV)
  • Tasks: INV-2, INV-9

Stories like these come out of a bigger feature. To split one into parts, stories and tasks, see how to break down a feature.

How to use it

How to fill it in, step by step.

Writing the story takes a minute. Most of the value comes from the conversation it triggers and the criteria you agree on during it.

  1. 01Name the role precisely. “User” is not a role. Use the roles your product has: owner, admin, member, invitee. Different roles often mean different stories.
  2. 02Write the want in the user’s words, then ask “so that what?” until the answer is something the person gets, not something the system does.
  3. 03Add the criteria and the edge cases. Take the happy path first, then the wrong account, the expired link, the empty list and the missing permission.
  4. 04Cut anything that is a separate story. If the worst case does not fit in a sprint, or two people would build it independently, split it.
  5. 05Estimate as a range with the people who will build it. Write down what drives the worst case; it often points to an open question.
  6. 06Link the story to its plan. Keep the design, the parent plan and the tasks together so a question about the story can be checked against them.

Skip the blank page

Let SprintProof draft it with you.

Describe the feature and the planner asks the questions a reviewer would, then drafts the brief, done-when, not-now and parts with ranges. The check library adds the edge cases teams usually find mid-sprint.

Turn this into a reviewed plan

FAQ

User story questions

What is a user story?
A user story is a short description of something a person wants from the product, written as “As a [role], I want [action], so that [outcome]”. It is kept small enough to build in one sprint and comes with acceptance criteria that say when it is done.
What does INVEST mean?
INVEST is a checklist for a good story: Independent, Negotiable, Valuable, Estimable, Small and Testable. If a story fails one of these, it usually needs splitting, a clearer outcome or an answer to an open question.
What is the difference between a user story and a task?
A story describes an outcome for a person and can be checked by using the product. A task is a piece of work that helps deliver it, such as a migration or an API route, and has no user-facing outcome on its own. A story usually breaks down into several tasks.
How many acceptance criteria should a story have?
Usually three to seven. Fewer may mean the edge cases are missing; many more usually means the story is too big. Each one should be something a tester can answer yes or no to.
How do I use the template in Jira, Linear or Notion?
Copy it with the button on this page and paste it into the description field. Linear, Notion and GitHub issues turn the Markdown into headings and checklists. Jira converts most of it; check the checklists after pasting. Or download the .md file and import it.

Turn this into a reviewed plan with SprintProof.

Describe the feature and SprintProof turns it into a plan: checked against a library of questions reviewers ask, estimated as a range with 50, 80 and 90% dates, and signed off before anyone starts.