writing-prd

Write complete, testable PRDs with acceptance tests and readiness checks.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill writing-prd-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-prd
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spx-legacy/skills/writing-prd
Command: npx skills add https://github.com/outcomeeng/claude --skill writing-prd-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD development often suffers from incomplete problem statements, vague outcomes, and unclear scope. This skill provides a structured framework to identify user problems, design measurable outcomes, define scope, and compose ready-to-deliver PRDs.

Core Features & Use Cases

  • Guided discovery of user problems and customer journey
  • Measurable outcome design with evidence of success
  • Complete PRD composition with scope, approach, and open decisions
  • Open questions and ADR/PDR triggers to inform decision-making

Quick Start

Prompt Claude Code to initiate a PRD using the guided workflows and fill sections with vetted user problems, outcomes, and scope.

Frequently Asked Questions about writing-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD with measurable outcomes and acceptance tests?

To write a PRD with measurable outcomes, use a structured framework to define user problems, design evidence-based success metrics, and compose Gherkin acceptance tests for clear scope.

How do I write Gherkin acceptance tests in a product requirements document?

Writing Gherkin acceptance tests in a PRD involves defining clear end-to-end scenarios during scope definition, ensuring every feature has testable criteria before development begins.

What is the best way to structure a PRD for a complex feature?

The best way to structure a complex feature PRD is by separating problem understanding, outcome design, and scope definition, while including open questions and ADR triggers for decision-making.

How do I define measurable outcomes for a product requirements document?

Defining measurable outcomes for a PRD requires guided discovery of customer journeys to establish evidence of success, ensuring the product scope directly targets vetted user problems.

When should I trigger an ADR or PDR during PRD development?

You should trigger an ADR or PDR during PRD development when open questions or architectural decisions arise, documenting these triggers within the scope to inform downstream decision-making.

Does this PRD framework support project, capability, and feature levels?

Yes, this PRD framework supports project, capability, and feature levels by providing tailored workflows for problem understanding, outcome design, and readiness checks across varying scopes.