# Feature Spec

> A lightweight spec process that aligns on the problem, the user, and the done criteria before any code is written.

**Category:** Product & Engineering

**When to use:** Before building any feature larger than a small change.

**Trigger:** A feature is prioritized for build

## Steps

1. State the problem and the user it is for in plain language, with evidence it matters.
2. Define what success looks like and how you will measure it.
3. Sketch the proposed solution and the main alternatives you considered.
4. List what is explicitly out of scope for this version.
5. Write the acceptance criteria as a checklist a reviewer can verify.
6. Review the spec with engineering and one user-facing voice before building.

## Outputs

- A short spec with problem, success metric, and scope
- Acceptance criteria as a verifiable checklist
- An out-of-scope list

## Tools

- Docs
- Issue tracker

## Notes

The out-of-scope list prevents more rework than the spec itself. Saying what you are not building is half of saying what you are.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/feature-spec
Run it live with your humans and AI agents at https://orgtp.com.