prd

Name: prd
Availability: InStock
Author: speqqai

Generate production-grade PRDs with two-tier requirement tables and acceptance criteria.

Updated Apr 27, 2026

Search Tags:#requirements #validation #traceability #prd #production-grade #two-tier

Ready to run

npx skills add https://github.com/speqqai/claude --skill prd-speqqai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/speqqai/claude/tree/main/skills/create-prd
Command: npx skills add https://github.com/speqqai/claude --skill prd-speqqai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Produces production-grade PRDs that are ready for PM and engineering review, reducing ambiguity and rework by providing a formal, implementation-ready document.

Core Features & Use Cases

Structured two-tier PRD format with a summary table and detailed tables per requirement.
Reference-standard workflow (prd-standard.md, prd-template.md, validation-rubric.md) loaded in order to ensure gates are respected and validation performed.
Clear user outcomes for PMs and engineers with traceability from goals to requirements and acceptance criteria.

Quick Start

Provide a scope-aligned brief and I will generate a production-grade PRD using the canonical two-tier tables.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I write a production-grade PRD ready for engineering review?▼

A production-grade PRD requires a canonical two-tier format with summary and detail tables, ensuring traceability from goals to capabilities and acceptance criteria. Apply reference standards and execute a preflight checklist to validate scope and personas before ship.

What is the two-tier requirements format for product requirement documents?▼

The two-tier requirements format structures a PRD using a summary table for high-level overview and detailed tables for individual requirements. This ensures explicit scope, personas, and goals while maintaining traceability to acceptance criteria.

How do I ensure traceability from goals to acceptance criteria in a PRD?▼

Traceability from goals to acceptance criteria is achieved by structuring requirements with explicit scope and personas, then mapping capabilities directly to measurable metrics. A validation rubric verifies these links before the document ships.

Can I generate an implementation-ready PRD from a brief scope description?▼

Yes, providing a scope-aligned brief allows the generation of an implementation-ready PRD. The process applies standard references like prd-template.md and validation-rubric.md to produce user outcomes suitable for PM and engineering review.

What validation standards are needed to ship a production-grade PRD?▼

Shipping a production-grade PRD requires applying prd-standard.md, prd-template.md, and validation-rubric.md in sequence. These references enforce gates and execute a final preflight checklist to reduce ambiguity and rework.

Why does my PRD require a preflight checklist before PM review?▼

A preflight checklist is required to ensure the PRD is production-grade and ready for PM review. It validates that the two-tier tables, scope, personas, and acceptance criteria align with the standard references before ship.