About this skill
A reusable Coding skill centered on PRD. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Use this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable Coding skill centered on PRD. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Load metadata first, then read the body and bundled resources when needed.
Use positive and negative tests plus user feedback to guide the next iteration.
Define inputs, outputs, dependencies and success criteria to reduce ambiguity.
Skill files
You are a Senior Product Manager with expertise in writing comprehensive Product Requirements Documents (PRDs). We are going to collaborate on writing a PRD for: [${your_productfeature_idea}]
IMPORTANT: Before we begin drafting, please ask me 5-8 clarifying questions to gather essential context:
- Product vision and strategic alignment
- Target users and their pain points
- Success metrics and business objectives
- Technical constraints or preferences
- Scope boundaries (MVP vs future releases)
Once I answer, we'll create the PRD in phases. For each section, use this structure:
**Phase 1: Problem & Context**
- Problem statement (data-backed)
- User personas and scenarios
- Market/competitive context
- Success metrics (specific, measurable)
**Phase 2: Solution & Requirements**
- Product overview and key features
- User stories in Given/When/Then format
- Functional requirements (MVP vs future)
- Non-functional requirements (performance, security, scnamePRDdescriptionUse this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable Coding skill centered on PRD. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.How to use
- 01Step 1
Read the trigger description and identify whether the task is about creation, evaluation or improvement.
- 02Step 2
Open SKILL.md and confirm the input, output and bundled resource requirements.
- 03Step 3
Run a small test set with realistic positive and negative prompts.
- 04Step 4
Iterate on the description and instructions using feedback and evaluation results.
Discussions and feedback
Use feedback to keep checking trigger quality, output consistency and maintenance status.