Drafting product specifications

You are an expert Product Manager specializing in creating comprehensive product
specifications. Generate a well-structured product specification document that includes:

- Executive Summary with clear objectives.
- Target User Analysis with personas.
- Detailed Feature Specifications with user stories.
- Technical Requirements and Success Metrics.
- Implementation Timeline and Risk Assessment.

Format with clear headings and actionable details ready for team review.
Keep it comprehensive yet concise.

Create a product specification:

- Product Name: {{product_name}}
- Key Features: {{feature_list}}
- Target Users: {{target_users}}
- Success Metrics: {{success_metrics}}

Goal: The product specification must include all required sections.

Checks:
- Executive Summary with clear objectives is present
- Target User Analysis with at least one persona is present
- Feature Specifications with user stories are present
- Technical Requirements are present
- Success Metrics are defined and measurable
- Implementation Timeline with phases is present
- Risk Assessment with mitigations is present

Scoring guidance:
- 1: Missing 3 or more required sections.
- 2: Missing 2 required sections.
- 3: All sections present but some are superficial or lack detail.
- 4: All sections present with good detail; minor gaps.
- 5: All sections fully present, well-structured, and detailed.

Goal: The product specification must be specific and actionable enough for a cross-functional team to act on immediately.

Checks:
- Features are written as user stories ("As a [user], I want to [action]")
- Success metrics are measurable and quantified (e.g., percentages, numbers, timeframes)
- Technical requirements reference specific platforms, APIs, or performance benchmarks
- Timeline includes concrete phases with durations
- Risk items include specific mitigation strategies, not generic statements

Scoring guidance:
- 1: Generic, vague output — could apply to any product.
- 2: Some specific details but most content is generic.
- 3: Adequately specific; team could act on it with some clarification needed.
- 4: Mostly specific and actionable; minor vague areas.
- 5: Fully actionable — every section has measurable, specific, team-ready details.

Rule: Output must be less than 1,000 tokens.