skills.rest
albertattard
albertattardCOMMUNITY
Explore all skills by this author →
Website𝕏@java_creedGitHub

derive-product-requirements-document

Convert scope documents and feature descriptions into detailed PRDs.

3|Updated Apr 28, 2026
Search Tags:#clarification#product development#product requirements#PRD generation#scope analysis
One-click install
npx skills add https://github.com/albertattard/skills --skill derive-product-requirements-document
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: derive-product-requirements-document
Source: https://github.com/albertattard/skills/tree/main/skills/derive-product-requirements-document
Command: npx skills add https://github.com/albertattard/skills --skill derive-product-requirements-document

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists product teams in converting broad or clarified scope documents into detailed, actionable Product Requirements Documents (PRDs), ensuring clarity and alignment before development begins.

Core Features & Use Cases

  • Scope Conversion: Translates scope artifacts such as scope files and feature descriptions into structured PRDs.
  • Clarification Loop: Helps ask targeted questions to resolve ambiguities and unresolved decisions.
  • Workflow Guidance: Guides users through a systematic process to define acceptance criteria, constraints, risks, and user journeys for product features.

Quick Start

Use the derive-product-requirements-document skill to automatically generate a detailed product requirements document from your project scope or feature description files.

Frequently Asked Questions about derive-product-requirements-document

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

FAQPage Schema
How do I generate a product requirements document from a scope document?▼

To generate a product requirements document, this Skill converts scope files and feature descriptions into structured PRDs by analyzing ambiguities and defining acceptance criteria through an interactive clarification process.

What is the best way to identify ambiguities and constraints in product scope?▼

Identifying ambiguities and constraints in product scope is handled by an interactive clarification loop that asks targeted questions to resolve unresolved decisions before development begins.

How do I define acceptance criteria and user journeys for feature development?▼

Defining acceptance criteria and user journeys for feature development is achieved by guiding users through a systematic workflow that translates broad product scope into actionable requirements.

Can I use a feature description file to create a PRD for slicing workflows?▼

Yes, you can use feature description files to create a PRD suitable for slicing workflows, as the Skill directly translates scope artifacts into comprehensive documents guiding development.

Does PRD generation work without predefined constraints and risk analysis?▼

PRD generation includes defining constraints and risks systematically, ensuring product teams achieve clarity and alignment by resolving missing decisions through targeted questions rather than skipping them.

Related Skills

Explore More Product & Management Skills→
JoshMockJoshMock
22

speckit-specify

Convert natural language feature descriptions into validated structured specifications.

Community
Intermediate
Yeachan-HeoYeachan-Heo
32.6k

ralph-init

Generate a PRD with goals, constraints, and implementation phases from a project description.

Community
Intermediate
skycruzerskycruzer

Launch Planner

Transform unvalidated app ideas into actionable MVP plans with lean PRD structures.

Community
Basic
Lands-1203Lands-1203
40

f2s-req-clarify

Clarify PRDs through targeted questions and generate a clarification document.

Community
Intermediate