PRD Phase Skill

Generate structured PRDs from feature prompts using a phase-gate process.

9|2|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ilandahan/AID --skill prd-phase-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: PRD Phase Skill
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/memory-system/references/phases/prd
Command: npx skills add https://github.com/ilandahan/AID --skill prd-phase-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The PRD Phase Skill streamlines the creation of thorough product requirement documents by applying a deterministic phase-gate process to feature prompts, reducing manual drafting, misalignment, and rework.

Core Features & Use Cases

  • Deterministic PRD generation using a phase-gate model.
  • Structured PRD outputs with goals, scope, acceptance criteria, success metrics, and traceability to artifacts.
  • Use Case: turn a feature idea into a complete PRD ready for review with PM, Dev, and QA alignment.

Quick Start

Invoke the PRD Phase Skill with a feature prompt: /prd [feature-name]. The generated PRD will be saved to docs/prd/YYYY-MM-DD-[feature-name].md and includes sections for goals, scope, acceptance criteria, and metrics.

Frequently Asked Questions about PRD Phase Skill

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

FAQPage Schema
How do I automate PRD creation from a feature prompt?▼

Automating PRD creation involves applying a deterministic phase-gate process to feature prompts, generating structured documents with objectives, acceptance criteria, and success metrics. This reduces manual drafting, misalignment, and rework.

What is a phase-gate process for product requirement documents?▼

A phase-gate process for product requirement documents applies a standardized prompting sequence to feature scoping, ensuring structured outputs with goals, scope, and traceability. It targets product discovery and requirements gathering across PM, engineering, and QA teams.

How do I generate a PRD with acceptance criteria and success metrics?▼

Generating a PRD with acceptance criteria and success metrics requires invoking a standardized prompting sequence with a feature name. The output is saved as a markdown file, including structured sections for goals, scope, metrics, and traceability to artifacts.

Can I use this deterministic PRD generation for cross-functional team alignment?▼

Yes, deterministic PRD generation targets cross-functional alignment for PM, Dev, and QA teams. By applying a phase-gate model to feature prompts, it produces complete requirement documents ready for review, reducing misalignment and manual rework.

What's the best way to structure feature specs for traceability?▼

The best way to structure feature specs for traceability is using a standardized phase-gate sequence that maps goals, scope, and acceptance criteria to artifacts. This deterministic approach ensures complete, review-ready requirement documents.