Spec-first examples you can actually reuse

Use these case studies to see how a loose request becomes a small working packet: spec.md, tasks, acceptance criteria, and test evidence before AI coding starts.

BeforeWeak ticket or prompt
AfterReviewable spec packet
UseCopy into issues and PRs

Featured case studies

Checkout coupon code

A money-touching checkout request becomes a bounded spec with validation states, total calculation, implementation tasks, and rollback evidence.

Weak request:
Add coupon codes to checkout.
Make sure invalid codes do not break payment.

Spec boundary:
- one coupon before payment
- no admin UI
- no totals refactor
Open the coupon case

API error taxonomy

An API error cleanup request becomes a stable contract with compatibility notes, SDK fixtures, OpenAPI examples, and migration evidence.

Weak request:
Improve API errors.
Make them easier for clients to handle.

Spec boundary:
- envelope only
- additive response change
- old SDKs still parse
Open the API error case

Quick before/after examples

Notification preferences

Turn a broad settings request into migration risks, preference states, and duplicate-send evidence.

Report export

Turn "CSV for large accounts" into async export tasks, stale-filter risks, and load-test evidence.

More compact rewrites

Compare loose tickets against spec packet versions for scope, tasks, acceptance, and evidence.

Browse quick examples

Start from your own vague request

Paste a messy requirement into the AI Coding Spec Packet generator and turn it into four reviewable Markdown files.

Generate a spec packet Open feature spec template

Editorial note

Examples are selected for practical reuse: each case must show a real before/after move, a spec boundary, and review evidence.