Write User Story

User Story Structure

Every story must have these sections (in order):

1. Purpose/Overview — What it achieves and why. Include business context, user persona, and links. Optionally add a Technical Details/Approach sub-section for architectural decisions without over-specifying implementation.
2. Requirements/Scope — Functional requirements (specific, measurable). Non-functional requirements only when they have measurable impact. Out of Scope only when genuine ambiguity exists.
3. Acceptance Criteria — Testable conditions in Given-When-Then format.
4. Testing Guidance — Manual testing scenarios only. No unit/integration test specs.

Template

## Purpose/Overview

[High-level description of what this story achieves and why it's important.
Include business context, user persona, and links to related work.]