# [Feature name]: feature spec

**Owner:** [name] · **Status:** Draft · **Last updated:** [date]
**Reviewers:** [product] · [engineering] · [design] · [area owners]

> Free feature spec template from SprintProof: https://sprintproof.com/templates/feature-spec-template
> Replace everything in [brackets]. Delete the guidance lines (starting with ">") when you are done.

## 1. Overview

> The feature in a few lines, and what has to be true for it to count as done. Link the PRD instead of repeating it.

- **Builds on:** [link to the PRD or brief]
- **The user gets:** [what changes for them]
- **Done when:**
  - [ ] [A user can ...]
  - [ ] [... still works when ...]

## 2. Scope and not now

> What this spec covers and what it leaves out, each cut with a reason.

- **In:** [flow or area]
- **Not now:** [item]: [reason]

## 3. Frontend parts

> Each screen or component, with what the user does, the states it handles and the sizes and input methods that count.

| Part | Behaviour | States and edge cases | Best (days) | Likely (days) | Worst (days) |
| --- | --- | --- | --- | --- | --- |
| [screen or component] | [what it does] | [empty, loading, error, no access, small screen, keyboard] | | | |

## 4. Backend parts

> Endpoints, jobs and rules. For each: who may call it, what it returns and the error codes.

| Part | Behaviour | States and edge cases | Best (days) | Likely (days) | Worst (days) |
| --- | --- | --- | --- | --- | --- |
| [endpoint, job or rule] | [inputs, result, permissions] | [error codes, retries, duplicates, limits] | | | |

## 5. Data parts

> Tables, columns, indexes and migrations. Say how long the migration takes on a copy of production, and how you undo it.

| Part | Behaviour | States and edge cases | Best (days) | Likely (days) | Worst (days) |
| --- | --- | --- | --- | --- | --- |
| [table or migration] | [columns, indexes] | [migration time, rollback] | | | |

## 6. Cross-cutting parts

> Permissions, tests, logging, limits, documentation. Give each its own estimate.

| Part | Behaviour | States and edge cases | Best (days) | Likely (days) | Worst (days) |
| --- | --- | --- | --- | --- | --- |
| [permissions, tests, limits] | [what it covers] | [what it must prove] | | | |

## 7. Edge cases and open questions

> Each edge case becomes a part or an open question. Every question needs an owner and a date to decide by.

| Question | Owner | Decide by | Answer |
| --- | --- | --- | --- |
| [question] | [name] | [date] | |

## 8. Estimate

> A range, never one number. Sum the parts and say which one has the widest spread and why.

- **Total:** [best] to [worst] days, likely [likely]
- **Widest spread:** [part]: [why it is uncertain]
- **Adds parts if answered "yes":** [open question]
- **Date at 80% confidence:** [date]
