Spec Feature

Outcome

Builders can implement and verify one bounded change without inventing product intent.

Why It Matters

A detailed specification can efficiently build an unneeded feature. Demand and beneficiary progress come first.

Use When

Use only after observed demand makes implementation the first unresolved job.

Inputs

Bring demand evidence, beneficiary, present behavior, desired outcome, baseline, constraints, authority, dependencies, acceptance, evidence, and rollback.

Recipe

1. State the user situation and valuable change. 2. Cite demand evidence and unknowns. 3. Bound behavior, data, states, errors, access, and non-goals. 4. Define acceptance and observable proof. 5. Name dependencies, rollout, review, and rollback.

Human and AI Control

AI may explore options and draft tests. Humans own product priority, trade-offs, security, consent, release, and outcome judgment.

Output and Handoff

Return a feature contract with story, scope, interfaces, constraints, acceptance tests, proof plan, owner, and rollback.

Evidence, Transfer, and Stop

Passing tests proves conformance, not beneficiary value. Stop when the feature outruns demand or cannot be safely reversed.

Next

After observed use reaches review, review the beneficiary outcome.