skills.rest
AlmogMaayan
AlmogMaayanCOMMUNITY
Explore all skills by this author →
GitHub

ptp-prd

Generates epic-scoped product requirements documents from selectors or free-text change descriptions.

Updated Jun 8, 2026
Search Tags:#documentation#change management#prd#product requirements#openspec#epic#requirements generation
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-prd-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-prd
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-prd
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-prd-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a PRD for a change request is slow and inconsistent, and teams often skip it entirely. This Skill turns a free-text feature description or an existing change selector into a structured, epic-scoped PRD written directly into the OpenSpec change folder, with no interactive prompts. ## Core Features & Use Cases - Selector projection: Maps bare change ids, epic:XXXX, story:NN, or omitted arguments onto the set of active epics, producing exactly one PRD per epic. - Free-text producer path: Accepts a plain-language description, allocates a fresh epic (XXXX_01_<desc>), creates the change folder, and authors the PRD there. - Graceful degradation: Uses the prd-taskmaster plugin's prd:generate when available (MCP or script.py backend), and falls back to inline authoring with a 10-section minimum PRD schema when the plugin is absent or produces no output. - Use Case: Run /ptp:prd add oauth login support to allocate a new epic and receive a complete PRD at openspec/changes/<id>/prd.md, ready for /ptp:plan. ## Quick Start Ask the assistant to run /ptp:prd with a short description of your feature, such as "/ptp:prd add oauth login support", to generate a PRD in the new change folder.

Frequently Asked Questions about ptp-prd

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

FAQPage Schema
How do I generate a PRD from a feature description?▼

Pass a free-text description to /ptp:prd, such as "/ptp:prd add oauth login support". The skill allocates a fresh epic, creates the change folder under openspec/changes/, and writes a structured PRD to prd.md there.

How do I write a PRD for an existing epic or story?▼

Use a selector like epic:0019, story:02, or a bare change id. The skill projects the selector onto its epic and writes one PRD per epic to the change folder of the epic's lowest-numbered story.

Does PRD generation work without the prd-taskmaster plugin?▼

Yes. When the prd-taskmaster plugin or its backend is absent, the skill authors the PRD inline using a 10-section minimum schema covering problem, goals, scope, requirements, acceptance criteria, risks, and open questions.

Where is the generated PRD file saved?▼

The PRD is written to openspec/changes/<id>/prd.md, where <id> is the epic's lowest-numbered story across active and archived changes. No separate openspec/prds/ directory is created, and re-running overwrites the same path deterministically.

Can I combine multiple epics into one PRD?▼

No. The skill always produces exactly one PRD per epic. Combined multi-epic PRDs are explicitly out of scope because no selector form names a unified multi-epic initiative.

Related Skills

Explore More Product & Management Skills→
mufengbufengmufengbufeng
1

openspec-propose

Generate proposal, design, and task artifacts for requested changes via openspec CLI.

Community
Advanced
dailydmdailydm

implement

Translate breakdown tasks into implementation plans and code changes.

Community
Advanced
AnthemFlynnAnthemFlynn

openspec-finishing-branch

Validate tests, select a merge/PR option, and archive OpenSpec changes.

Community
Advanced
YuriNakayamaYuriNakayama

research-prompt-builder

Translate user intent into structured YAML research prompts via interactive hearings.

Community
Advanced