# Product specification · [Feature] · v[n] · [Date] **Owner:** [PM] **Design:** [name] **Engineering:** [name] **Status:** Draft / In review / Approved ## 1. Context and linked insights | Insight ID | Insight (one sentence) | Confidence | |---|---|---| | | | | Other drivers (strategic, compliance, technical): [list, named as drivers] ## 2. Users and buying-group roles affected [End users, champion, economic buyer, technical evaluator, procurement, partner] ## 3. Goals, non-goals and success metrics - Goals: - Non-goals: - Success metrics with baselines and review date: ## 4. Functional requirements | Req ID | Requirement | Traces to | Acceptance criterion (Given, When, Then) | Priority | |---|---|---|---|---| | REQ-[xx] | | INS-[xx] | Given [context], when [event], then [observable outcome] | | ## 5. Behavioral design decisions | Decision (default, framing, choice set, prompt) | Choice made | Rationale | Four-test result | |---|---|---|---| | | | | | ## 6. AI behavior (AI features only) - Expected outputs and format: - When to decline, ask or escalate: - How evidence and confidence are shown: - Evals that gate release, with thresholds: - Human approval points and what the approver sees: ## 7. Non-functional requirements Security and access, audit logging, latency, availability, data residency, accessibility, cost per action. ## 8. Risks and review results - Behavioral design review outcome: [link and verdict] - Open questions: - Risks and mitigations: ## 9. Traceability | Insight ID | Opportunity or job | Req ID | Acceptance criterion | Success metric | Verification (test or eval) | Status | |---|---|---|---|---|---|---| | | | | | | | | Requirements with no upstream insight or named driver: [list or "none"] High-confidence insights with no decision: [list or "none"]