User Stories¶
User stories capture what Loryth users need and why. They bridge the gap between personas (who uses Loryth) and requirements (what we build).
Format¶
Each story follows the standard format:
As a {persona}, I want {action}, so that {outcome}.
ID Scheme¶
Stories use the pattern US-{AREA}-{NNN}:
| Code | Area | Epic File |
|---|---|---|
| GRO | Grocery & meal planning | grocery.md |
| WAL | Financial tracking | wallet.md |
| JRN | Personal journaling | journal.md |
| KB | Knowledge base | kb.md |
| ISS | Task & issue tracking | issues.md |
| XC | Cross-service workflows | cross-cutting.md |
Priority Levels¶
- Must — Core functionality required for the service to be useful
- Should — Important features that significantly improve the experience
- Could — Nice-to-have features for future iterations
Epic Summary¶
| Epic | Stories | Primary Personas |
|---|---|---|
| Grocery | US-GRO-001 through US-GRO-008 | Tinkerer, Planner, Coordinator |
| Wallet | US-WAL-001 through US-WAL-008 | Tinkerer, Planner, Coordinator |
| Journal | US-JRN-001 through US-JRN-007 | Planner |
| KB | US-KB-001 through US-KB-007 | Tinkerer, Plugin Developer |
| Issues | US-ISS-001 through US-ISS-007 | Tinkerer, Coordinator |
| Cross-Cutting | US-XC-001 through US-XC-005 | All personas |