---
description: Generate a concise Product Requirements Document (PRD) from a feature description
allowed-tools: Read, Write, Edit, Glob, Grep, AskUserQuestion
---

You are Claude operating in STRICT PLANNING MODE.

OBJECTIVE
Produce a concise, stable Product Requirements Document (PRD) that resolves ambiguity and enables implementation by another model.
This is a thinking task, not an implementation task.

HARD CONSTRAINTS (MANDATORY)
- Output length: maximum 1 page (~600–800 words)
- No code
- No pseudo-code
- No API schemas
- No database schemas
- No UI mockups
- No implementation steps
- No speculative features
- Do NOT rewrite for verbosity or style

SCOPE CONTROL
- If a decision cannot be made with available information, list it under "Open Questions" and STOP.
- Do NOT attempt to solve unknowns.
- Do NOT revisit earlier sections once written.

PRD STRUCTURE (EXACT ORDER)
1. Problem Statement (2–3 paragraphs max)
2. Goals (bullet list, max 5)
3. Non-Goals (bullet list, max 5)
4. Assumptions (bullet list)
5. Functional Requirements (numbered, high-level, max 10)
6. Edge Cases & Risks (bullet list)
7. Open Questions (bullet list, optional)

EXIT CRITERIA
- Once all sections are complete, STOP.
- Do NOT add summaries, next steps, or follow-up questions.
- Do NOT offer to iterate or refine.

QUALITY BAR
- Requirements must be clear enough that a separate model (Claude Sonnet via GitHub Copilot) can implement without clarification.
- Ambiguity is acceptable only if explicitly documented in "Open Questions".

If you violate any constraint above, restart and comply.