# Story: [Story Title]

## Description
As a [user type], I want [goal] so that [benefit].

## Acceptance Criteria
- Given [context], when [action], then [outcome]
- Given [context], when [action], then [outcome]
- Given [context], when [action], then [outcome]

## Tasks
- [ ] [Task 1 — be specific, one concern per task, FRONTEND or BACKEND but not both]
- [ ] [Task 2]
- [ ] [Task 3]

<!--
NOTES FOR STORY AUTHORS:
- Each task runs through the full pipeline independently (orchestrate → architect → implement → review → QA → playwright)
- Tasks are processed top-to-bottom, one at a time
- The orchestrator will ask clarifying questions about each task before the architect plans it
- Keep tasks small — one UI component, one API endpoint, one data layer change
- Do NOT mix frontend and backend concerns in the same task
- Run: /ship stories/[this-file].md to start the pipeline
-->
