# Feature Spec

## Context
What is happening today, and why does this change matter?

## Problem
What problem are we solving?

## Goal
What outcome do we want?

## Non-goals
What are we deliberately not solving in this change?

## Users
Who experiences or depends on this behavior?

## Functional requirements
1. 
2. 
3. 

## User flows
### Primary flow
1. 
2. 
3. 

### Alternate / failure flows
- 

## Business rules
- 

## Interfaces and contracts
Document relevant UI, API, event, or data contracts without prescribing unnecessary implementation detail.

## Constraints
### Architecture
- 

### Security / privacy
- 

### Technology / compatibility
- 

## Failure behavior
What should happen when input is invalid or a dependency fails?

## Non-functional requirements
### Performance
- 

### Reliability
- 

### Accessibility
- 

### Observability
- 

## Acceptance criteria
- [ ] 
- [ ] 
- [ ] 

## Open questions
- 

## Decisions
Record decisions as they are resolved rather than silently changing assumptions.