User Story Block
Document user stories with the standard As a/I want/So that format, acceptance criteria, and agile metadata.
Overview
The User Story block captures requirements in the standard agile format: As a [user], I want [feature], So that [benefit]. It includes acceptance criteria with completion tracking, story points, sprint assignment, and status. Use this block to document user-centred requirements for agile development.
Feature User Story
A user story for a search feature with detailed acceptance criteria.
Completed User Story
A completed user story showing all acceptance criteria met.
Block Properties
| Property | Required | Description |
|---|---|---|
| storyId | No | Unique story identifier (e.g., US-1042) |
| title | Yes | Story title |
| asA | No | The user role |
| iWant | No | The desired functionality |
| soThat | No | The benefit or value |
| acceptanceCriteria | No | Array of criteria with criterion text and met status |
| priority | No | Priority level (critical, high, medium, low) |
| storyPoints | No | Story point estimate (1, 2, 3, 5, 8, 13, 21) |
| status | No | Status (backlog, ready, in-progress, in-review, done, blocked) |
| sprint | No | Sprint assignment |
| assignee | No | Assigned team or person |
| epic | No | Parent epic |
| notes | No | Additional notes |