Product requirements draft
What it does
Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
How to install it
In the web interface, open Context, then Skills, then Import, and choose Upload skill folder.
On the command line, copy the folder into .agents/skills/ in your project, or into ~/.vibe/skills/ to have it everywhere.
More in Product Management
Read the full skill in the source repository, part of awesome-mistral-vibe-skills, CC BY-SA 4.0. Not affiliated with, or endorsed by, Mistral AI.