prd

Generate structured Product Requirements Documents from feature ideas.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill prd-cmtkdot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/cmtkdot/arc/tree/main/skills/prd
Command: npx skills add https://github.com/cmtkdot/arc --skill prd-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD generation is time-consuming and error-prone when starting a new feature, leading to misalignment and slower execution.

Core Features & Use Cases

  • Structured PRD Drafting: Generates a complete PRD with executive summary, problem statement, goals, personas, and requirements, using plan-schema guidance.
  • Phase-driven Workflow: Guides clarification, quick research, scoring, and planning phases to ensure a comprehensive specification.
  • Validation & Governance: Validates against prd-schema and provides a reusable structure suitable for openspec consumption and stakeholder alignment.

Quick Start

Provide a feature concept and scope to generate a ready-to-review PRD.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a structured product requirements document from a feature idea?

To generate a product requirements document, provide a high-level feature concept and scope to trigger phase-driven drafting, producing an executive summary, problem statement, goals, personas, and requirements. This structured PRD aligns stakeholders and ensures comprehensive specification.

What sections are included in a standard PRD for feature planning?

A standard PRD for feature planning includes an executive summary, problem statement, goals, personas, and detailed requirements. This structure aligns with plan-schema and prd-schema validation to ensure comprehensive specification and stakeholder alignment.

Does PRD generation work with openspec consumption and plan-schema validation?

PRD generation validates output against prd-schema and integrates with plan-schema, producing a reproducible structure suitable for openspec consumption. This ensures the generated specification passes governance workflows and remains aligned with stakeholder requirements.

Can I use automated PRD drafting for governance workflows and stakeholder alignment?

Automated PRD drafting supports governance workflows by validating specifications against prd-schema and generating a reusable structure. This ensures stakeholder alignment during ideation and feature planning while maintaining a comprehensive, reproducible output.

What is the best way to start writing a specification for a new feature concept?

The best way to start writing a specification is providing a feature concept and scope to trigger a phase-driven workflow. This guides clarification, quick research, scoring, and planning phases to produce a ready-to-review, structured PRD.

Why does manual PRD generation cause misalignment during feature planning?

Manual PRD generation causes misalignment because starting a new feature is time-consuming and error-prone, leading to slower execution. Automated structured drafting applies plan-schema guidance to prevent these errors and ensure comprehensive specification.