prd

Create, critique, sync, and amend product requirements documents across teams.

Updated Mar 23, 2026

Search Tags:#workflow #versioning #requirements #prd #critique #product-management

Ready to run

npx skills add https://github.com/mattphanm/Codex-Agentic --skill prd-mattphanm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/prd
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill prd-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD lifecycle management is centralized, collaborative, and traceable, enabling teams to create, refine, sync, and amend product requirements with structured critique and integration surface discovery.

Core Features & Use Cases

Create new PRDs via the gather-criticize loop
Sync existing PRDs to spec groups and maintain versioned artifacts
Amend PRDs with implementation discoveries and maintain an amendment log
Resolve critiques through a structured, role-based review process
Integrate PRDs with spec workflows and memory-bank context for consistent governance

Quick Start

Invoke /prd to start a new PRD and follow the guided discovery loop.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I create a product requirements document with structured critique?▼

To create a product requirements document, invoke the guided discovery loop to gather requirements and automatically pass them through four role-based critics for structured critique. This ensures requirements are refined and aligned across teams before finalizing the PRD.

What is PRD lifecycle management and how does it handle versioning?▼

PRD lifecycle management is a centralized process that orchestrates creation, syncing, and amending of product requirements. It handles versioning by maintaining versioned artifacts with frontmatter metadata and tracking changes through an amendment log and decisions log.

How do I amend existing product requirements after implementation discoveries?▼

To amend existing product requirements after implementation discoveries, use the dedicated amender component to update the document and automatically maintain an amendment log. This keeps the PRD synchronized with actual development findings while preserving version history.

Can I sync PRDs to spec groups for cross-team alignment?▼

Yes, you can sync PRDs to spec groups to maintain cross-team alignment and discover integration surfaces. This seamless spec-group linking ensures consistent governance and connects product requirements directly to downstream spec workflows.

Does this PRD workflow require any specific dependencies or components?▼

No specific dependencies or external components are required to run this PRD workflow. It operates independently with a built-in writer, four critics, and an amender, enforcing a structured state machine and frontmatter metadata without external tool integrations.