Skip to content

A spec that reviewers actually finish.

Problem first, proposal second, open questions in a list someone owns. Reviewers sign the decision log at the bottom, so nobody asks “did we agree on this?” in the next sprint.

TEdited by TheoEngineering22.1k uses25 min to fill

All templates

Preview of the Product spec template

Spec: Rate limits for the public API

Spec: Rate limits for the public API

Author
TTheo
Status
In review
Reviewers
Sam, Ana
Decision by
Dec 4

One paragraph, no jargon: what is broken and who feels it.

Problem

Three customers sent more than 40,000 requests a minute last week. The API slowed down for everyone else, and support answered 26 tickets about it.

Proposal

  • 600 requests a minute per key, with a burst of 100
  • Headers that say how many requests are left
  • A clear 429 error that links to Rate limits guide

Open questions

Decision log

DateDecisionSigned
Nov 18Limit per key, not per accountTheo, Sam
Nov 20Burst of 100 requestsTheo

More like this

Teams who use this template usually keep these three next to it in the sidebar.

Browse all 24 in the gallery
  • Incident postmortem

    Timeline, impact, causes and follow-ups, written without blame.

    Engineering · 8.7k uses

  • Quarterly roadmap

    Bets for the quarter in one table, as a timeline for the all-hands.

    Product · 11.9k uses

  • Design critique

    Context first, then feedback sorted by what it asks the designer to do.

    Design · 9.6k uses

Your copy of product spec, ready in a click.

Free for personal use. Your team can start on Plus with a 14-day trial, no card needed.