product-speclisted

# 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. ## Workflow 1. Read effective repository and host guidance, then inspect the requested scope, existing product facts, conventions, affected consumers, and `git status --short` before proposing a write. 2. Select exactly one public mode: - **Feature Spec** (default): specify one feature and include only the user-visible states, data effects, dependencies, and acceptance needed for that slice. - **Foundation Spec**: use only for a new product, new product line, or explicit redefinition of the product boundary. - **Artifact Update**: update only an existing, explicitly named product fact source after write authorization. When an existing Foundation Spec already fixes the product boundary and passes its applicable Ready gate, preserve it. For a requested downstream implementation, select the smallest source-proven feature gap and write only its Feature Spec; do not reopen product positioning without contradictory evidence. 3. Apply the product scope gate before synthesis. Distinguish several surfaces of one connected feature from several independent features with different user jobs,