# Prd Writing > Guide users through a structured workflow for writing Product Use when this capability is needed. - Skill: `tomevault-io/prd-writing` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/prd-writing` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/prd-writing/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - 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-writing --- # PRD Writing Workflow Guide users through Context Gathering, Section Drafting, and Validation when writing PRDs. ## When to use Trigger when user mentions: "write a PRD", "product spec", "draft requirements", or starting a new feature/product initiative. Offer three stages, or work freeform if user declines. ## Stage 1: Context Gathering Ask the user: 1. What problem does this solve? 2. Who are the target user? 3. What's the success metric? 4. Technical constraints or dependencies? 5. Timeline or priority? 6. Existing template to follow? Encourage context dumping: user research, competitive analysis, architecture considerations, stakeholder requirements. Ask 5-8 clarifying questions based on gaps. Move to drafting when you can discuss trade-offs without needing basic explained. ## Stage 2: Section Drafting Suggest this structure (adjust to users' template): 1. **Overview** - Problem and solution summary 2. **Goals & Success Metrics** - What success looks like 3. **User Stories** - Who benefits and how 4. **Requirements** - Functional and non-functional 5. **Out of Scope** - What's excluded 6. **Dependencies & Risks** - Considerations 7. **Timeline** - Milestones (optional) For each section: ask clarifying questions -> brainstorm 5-10 items -> let user curate -> draft -> refine based on feedback. ## Stage 3: Validation Check completeness: - Problem clearly stated - Target users defined - Success metrics measurable - Requirements specific and testable - Scope boundaries clear - Dependencies and risks identified --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/xiechao06) — claim your Tome and manage your conversions.