---
name: story-template
description: Story log template for user stories. Use when creating new story documents or need story structure reference.
---

## Story Log

### Goal
[One-sentence description of what this story aims to achieve]

### Why
[Context and motivation - why is this change needed?]

### User Story
**As a [role], I want [capability], so that [benefit].**

### Acceptance Criteria

#### 1. [Category Name]
- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]
- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]

#### 2. [Category Name]
- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]

#### 3. Error Cases
- [ ] **Given** [error condition], **When** you [action], **Then** [expected error behavior]

### Verification Approach
[How will acceptance criteria be verified? Options: CLI commands, API calls, E2E tests, browser MCP tools, manual UI testing by PO, etc.]

### Out of Scope
- [Explicitly list what won't be done in this story]
- [Helps prevent scope creep and sets clear boundaries]

---

### Completed Work Summary
Not yet started.

### Acceptance Checks

**Status: Pending Product Owner Review**

Developer verification completed:
- [List what the developer manually verified]
- [Note any observations or findings]

**Awaiting product owner acceptance testing before marking this user story as complete.**

### Follow-ups / Open Risks

#### Addressed
- [Items that were concerns but have been resolved]

#### Remaining
- [Known limitations or technical debt]
- [Future considerations]
- [Potential risks to be aware of]