prd-schema

Validate PRDs against Arc's 100-point framework for structured sections and phased implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs often lack a consistent structure and objective scoring, leading to misalignment across teams. This Skill provides a standardized PRD structure and a 100-point scoring framework to ensure comprehensive, testable product requirements within Arc's planning workflow.

Core Features & Use Cases

  • Structured PRD Sections: Defines required sections (Executive Summary, Problem Statement, Goals & Metrics, Non-Goals, User Personas, Functional Requirements, Implementation Phases, Risks & Mitigations) and optional sections (Technical Architecture, Data Requirements, Integration Points, Accessibility, Internationalization) to ensure complete planning artifacts.
  • Scoring & Validation: Enforces a 100-point scoring framework to guide priority, risk, and implementation decisions, ensuring measurable success criteria.
  • Arc Workflow Integration: Aligns PRD artifacts with Arc's plan → spec → beads pipeline, enabling seamless consumption by /arc:core:plan and related components.

Quick Start

Create a new PRD using the Arc PRD schema and run the validator to confirm all required sections are present and properly populated.

Frequently Asked Questions about prd-schema

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

FAQPage Schema
How do I validate a PRD against a standardized scoring framework?

Validating a PRD against a standardized scoring framework involves checking for structured sections like Executive Summary and Functional Requirements. This Skill applies Arc's 100-point framework to ensure comprehensive product requirements and measurable success criteria.

What sections are required in a product requirements document for Arc's planning workflow?

Required sections in a product requirements document for Arc include Executive Summary, Problem Statement, Goals, Non-Goals, User Personas, Functional Requirements, Implementation Phases, and Risks. This Skill enforces these mandatory sections to ensure complete planning artifacts.

How does PRD validation integrate with the plan and spec pipeline?

PRD validation integrates with the plan and spec pipeline by aligning artifacts with Arc's plan to spec to beads workflow. This Skill ensures validated PRDs are structured for seamless consumption by Arc's core planning components.

Can I include technical architecture and data requirements in my PRD validation?

You can include technical architecture, data requirements, integration points, accessibility, and internationalization in your PRD validation. This Skill defines these as optional sections that enhance the core 100-point scoring framework.

Why do product requirements documents need a 100-point scoring framework?

A 100-point scoring framework for product requirements documents is needed to guide priority, risk, and implementation decisions objectively. This Skill enforces the framework to prevent team misalignment and ensure testable requirements.

What is the best way to structure implementation phases and risk mitigations in a PRD?

The best way to structure implementation phases and risk mitigations in a PRD is to align them with a 100-point scoring framework. This Skill validates that these sections are properly populated to support measurable success criteria.