Process Library

Feature Spec

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

Product & Engineering 6 steps
When to use

Before building any feature larger than a small change.

Trigger
Runs when: A feature is prioritized for build

The procedure

6 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
DocsIssue tracker
Note: 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.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
feature spec sop product requirements process prd template acceptance criteria product spec checklist

Related SOPs

Product & Engineering
Code Review
6 steps
Product & Engineering
Deploy
6 steps
Product & Engineering
Bug Triage
6 steps
Product & Engineering
Sprint Planning
6 steps
← Back to the Process Library