Contract
- Input: product idea, user feedback, business problem, stakeholder input.
- Output: PRD with problem, goals, user stories, acceptance criteria, metrics, timeline.
- Scope: writes PRD; does not make product decisions unilaterally.
- Rule: writes PRD; does not make product decisions unilaterally.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit ProdPrdWritingArtifact as both:
- JSON:
.agents/skills/platform/artifacts/prod-prd-writing/{identifier}.json
- Markdown view: same filename with
.md extension
Product Requirements Document
Turn a product idea into a structured PRD with aligned goals, measurable outcomes, and clear scope.
Process
1. Problem statement
- What problem does this solve for users?
- Who is affected? (user segment)
- How is it solved today? (workaround, competitor, manual process)
- What is the cost of not solving?
Completion criterion: problem clear; user segment defined.
2. Goals
- Business goal: revenue, retention, efficiency, market position.
- User goal: task completed faster / easier / with less error.
- Technical goal: system reliability, performance, maintainability.
- Measurable: each goal has a metric and target.
Completion criterion: goals with metrics saved.
3. User stories
For each user journey: "As a [user type], I want [action] so that [benefit]."
- Acceptance criteria per story: given / when / then; conditions for pass.
- Priority: must-have / should-have / nice-to-have.
Completion criterion: stories with acceptance criteria saved.
4. Success metrics
- Leading (predictive): feature adoption rate, time-to-first-value, error rate.
- Lagging (outcome): revenue impact, retention, NPS, customer satisfaction.
- Dashboard: how will metrics be tracked (analytics tool, telemetry, survey)?
Completion criterion: metrics table saved.
5. Constraints and risks
- Technical: dependencies, performance, security.
- Regulatory: compliance (GDPR, accessibility, financial regulations).
- Timeline: dependencies, holidays, team availability.
- Risk mitigation per item.
Completion criterion: risks with mitigation saved.
6. Timeline and milestone
- Milestones with dates and deliverables.
- Dependencies between milestones.
- Review points (design review, user testing, release readiness).
Completion criterion: timeline saved with milestones.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: prod-prd-writing-33category: "product"4maturity: "stable"5version: "1"6description: "Write Product Requirement Documents (PRDs) — problem statement, goals, user stories, acceptance criteria, success metrics, timeline — with stakeholder alignment."7license: "MIT"8capabilities:9 - apply prod prd writing methods within explicit product boundaries10 - analyze write product requirement documents (prds) — problem statement, goals, user stories, acceptance criteria, success metrics, timeline — with stakeholder alignment with assumptions, constraints, and failure modes11 - produce and validate a product artifact with evidence, decisions, and next steps12outputs: "PRD with problem, goals, user stories, acceptance criteria, metrics, timeline."13sideEffects: []14dependencies: []15stopCondition: "PRD saved; stakeholder alignment noted; metrics defined."16risk: "low"17trustTier: "1"18maxIterations: "5"19promptVersion: "2.0"20artifactType: "pull-request"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: ""24diataxis: "how-to"25tags: ["product"]26compatibility: []27approvalRequired: "false"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/prod-prd-writing-331---3233## Contract3435- Input: product idea, user feedback, business problem, stakeholder input.36- Output: PRD with problem, goals, user stories, acceptance criteria, metrics, timeline.37- Scope: writes PRD; does not make product decisions unilaterally.38- Rule: writes PRD; does not make product decisions unilaterally.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `ProdPrdWritingArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/prod-prd-writing/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Product Requirements Document6465Turn a **product idea** into a structured PRD with aligned goals, measurable outcomes, and clear scope.6667## Process6869### 1. Problem statement70- What problem does this solve for users?71- Who is affected? (user segment)72- How is it solved today? (workaround, competitor, manual process)73- What is the cost of not solving?7475**Completion criterion:** problem clear; user segment defined.7677### 2. Goals78- **Business goal:** revenue, retention, efficiency, market position.79- **User goal:** task completed faster / easier / with less error.80- **Technical goal:** system reliability, performance, maintainability.81- **Measurable:** each goal has a metric and target.8283**Completion criterion:** goals with metrics saved.8485### 3. User stories86For each user journey: "As a [user type], I want [action] so that [benefit]."87- Acceptance criteria per story: given / when / then; conditions for pass.88- Priority: must-have / should-have / nice-to-have.8990**Completion criterion:** stories with acceptance criteria saved.9192### 4. Success metrics93- **Leading** (predictive): feature adoption rate, time-to-first-value, error rate.94- **Lagging** (outcome): revenue impact, retention, NPS, customer satisfaction.95- **Dashboard:** how will metrics be tracked (analytics tool, telemetry, survey)?9697**Completion criterion:** metrics table saved.9899### 5. Constraints and risks100- Technical: dependencies, performance, security.101- Regulatory: compliance (GDPR, accessibility, financial regulations).102- Timeline: dependencies, holidays, team availability.103- Risk mitigation per item.104105**Completion criterion:** risks with mitigation saved.106107### 6. Timeline and milestone108- Milestones with dates and deliverables.109- Dependencies between milestones.110- Review points (design review, user testing, release readiness).111112**Completion criterion:** timeline saved with milestones.113114## Completion115116- the skill's completion criteria are explicitly checked117- the artifact is saved and validated118- any blockers or skipped validations are documented119- the next consumer is identified or the work is handed off120---121@include .agents/skills/platform/contract-base.xml