| name | Feature Spec |
| description | Turn a feature request into a scoped, buildable spec with a clear success measure. |
| category | Ops |
Feature Spec
Take a raw request and shape it into a spec engineering can build and everyone
agrees on.
When to use
- A feature is greenlit and needs definition before work starts.
- A vague request needs scoping before it can be estimated.
Steps
- State the problem and the user it is for, not the solution.
- Define the scope: what is in, what is explicitly out.
- Describe the flows and the key states and edge cases.
- Set the success measure and how it will be checked.
- Flag risks, dependencies, and open questions for the operator.
Output
A spec: problem, scope, flows, success measure, and open questions — following
the [[Engineering standards]]. Ready to estimate and build.