ptp-prd-full

Authors a PRD and runs its dual-reviewer review loop in one orchestrated pass.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-prd-full-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-prd-full
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-prd-full
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-prd-full-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a product requirements document and then getting it reviewed normally requires two separate commands with manual handoff in between. This skill removes that seam by authoring the PRD and immediately running the dual-reviewer (main agent plus reviewer agent, default Claude plus Codex) inline-fix review loop in a single invocation. ## Core Features & Use Cases - Two-phase orchestration: Phase A authors the PRD into openspec/changes/<id>/prd.md via the ptp-prd skill; Phase B runs the full ptp-review-prd-full dual-reviewer loop without re-confirming scope. - PRD gate: If Phase A fails to write the PRD, the skill stops before Phase B and reports the failure with a recovery recommendation. - Pre-resolved inputs: Consumes the already-resolved epic selector, codex.mode decision, branch guard, and model target from the outer command session without re-resolving them. - Multi-epic support: Runs author, gate, and review sequentially per epic, with one review tally table per epic. - Use Case: A product engineer types /ptp:prd-full <epic> and receives a written PRD plus a converged Claude-and-Codex review, with a terminal report recommending /ptp:plan <change-id> as the next step. ## Quick Start Run the /ptp:prd-full command with an epic selector to author the PRD and immediately review it with both reviewers.

Frequently Asked Questions about ptp-prd-full

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

FAQPage Schema
How do I write and review a PRD in one command?▼

Run /ptp:prd-full with an epic selector. The skill authors the PRD into openspec/changes/<id>/prd.md, then immediately runs the dual-reviewer review loop without requiring a separate review command or scope re-confirmation.

What is the difference between ptp-prd and ptp-prd-full?▼

ptp-prd only authors the PRD and stops, recommending a separate review step. ptp-prd-full combines authoring and the full dual-reviewer review loop in one pass, passing the resolved epic explicitly between phases.

Does the PRD review require Codex to be installed?▼

Codex is optional and controlled by the codex.mode setting. Under required mode without codex on PATH the command stops before the skill runs; under auto or off the review proceeds and may report a mode-skip terminal state.

What happens if the PRD file is not written during authoring?▼

The prd-gate stops the skill before the review phase. It reports that Phase A failed to write the PRD and recommends running /ptp:prd to debug, then re-running /ptp:review-prd-full for the review.

Can ptp-prd-full handle multiple epics at once?▼

Yes. For a multi-epic selector it runs author, gate, and review sequentially per epic, writing one review marker per epic and printing a separate review tally table inside each epic's report block.