product

Turns an idea, feature request, product change, or ambiguous bug behavior into a minimal, verifiable feature contract (outcome, behavior, acceptance, out-of-scope) that an implementing agent can build without inventing requirements. Use this whenever a request leaves behavior, scope, or "what counts as done" open - new features, product changes, "should we build X", requests that feel too big, requests with a risky or irreversible side effect, or any time the user asks for scoping, shaping, acceptance criteria, a spec, or product thinking before implementation. Also use before handing non-trivial work to engineering or design agents. Skip when the expected behavior is already fully defined, such as a pure refactor, styling tweak, dependency bump, or a bug with a clear expected result.