Product Specification

Overview

Turn product ambiguity into the smallest repository-grounded specification that can authorize one implementation slice. Own product behavior, scope, business rules, user-visible states, acceptance, and explicitly authorized product-fact writes. Keep technical design and source mutation with their existing owners.

Consume urn:skills:product-request:v1; the portable typed handoff is urn:skills:product-contract:v1. Product Markdown remains the human product-behavior authority; the handoff carries stable document, decision, acceptance, and authority references without copying the document body or claiming implementation or delivery state.

Workflow