# Prd > Create or refine product requirements documents for feature ideas, MVPs, and roadmap items. Use when the user asks for PRDs, requirements, scope definition, user stories, success metrics, non-goals, or implementation-ready feature specs. Use when this capability is needed. - Skill: `tomevault-io/prd-9` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/prd-9` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/prd-9/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/prd-9 --- # PRD ## Overview Create developer-readable PRDs with clear scope, explicit assumptions, and measurable outcomes. ## Workflow 1. Analyze the request and infer all available context before asking questions. 2. Ask 3-5 clarifying questions only for information that materially changes scope or requirements. 3. Draft the PRD using the standard structure in `references/prd-structure.md`. 4. Mark unknown details as assumptions; avoid blocking on non-critical ambiguity. 5. Save the document with date-prefixed naming. 6. Ask whether the user wants revisions or task breakdown next. ## Output Rules - Use filename format: `YYYY-MM-DD__prd.md`. - Save to `personal/projects//drafts/` if project context is active. - Otherwise save to `personal/drafts/`. - Do not start implementation unless explicitly requested. ## References - Read `references/prd-structure.md` for required sections, question format, and quality checks. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jdworkdog) — claim your Tome and manage your conversions.