skills.rest
chidekina
chidekinaCOMMUNITY
Explore all skills by this author →
GitHub

prd

Create structured PRD Markdown and YAML spec files from user prompts.

2|7|Updated Feb 22, 2026
Search Tags:#planning#documentation#requirements#spec#product#prd
One-click install
npx skills add https://github.com/chidekina/aria-superpowers --skill prd-chidekina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/chidekina/aria-superpowers/tree/main/skills/prd
Command: npx skills add https://github.com/chidekina/aria-superpowers --skill prd-chidekina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and documenting complex features is time-consuming and error-prone, requiring a structured PRD with clear goals, scope, and acceptance criteria.

Core Features & Use Cases

  • Guided PRD creation: Collects user prompts and 3–5 clarifying questions, then outputs a formatted PRD and a machine-readable spec.
  • Structured PRD outputs: Produces two artifacts: a markdown PRD saved under tasks/prd-[feature-name].md and a YAML spec under tasks/spec-prd.yaml.
  • Usage scenarios: Plan new features, start new projects, or document requirements for upcoming work.

Quick Start

Describe a feature and I will generate a complete PRD and a machine-readable spec for it.

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 from a feature idea?▼

To create a Product Requirements Document, you provide a feature prompt and answer 3–5 clarifying questions, which generates a structured Markdown PRD and a machine-readable YAML spec.

What is the best way to document project requirements for upcoming work?▼

Documenting project requirements is best handled by generating structured PRDs with clear goals and acceptance criteria, outputting both a Markdown file and a YAML spec for machine readability.

Can I generate a machine-readable YAML spec alongside my PRD?▼

Yes, you can generate a machine-readable YAML spec alongside your PRD, with both artifacts saved automatically as spec-prd.yaml and prd-[feature-name].md in the tasks directory.

Do I need to manually structure goals and acceptance criteria when planning a new feature?▼

No, you do not need to manually structure goals and acceptance criteria, as the guided process asks essential clarifying questions to automatically build structured requirements into the PRD.

What is the process for turning a brief project description into a structured PRD?▼

Turning a brief project description into a structured PRD involves submitting a user prompt, answering targeted clarifying questions, and receiving formatted Markdown and YAML outputs.

Are there limitations to using guided PRD generation for complex feature planning?▼

Guided PRD generation relies on user-provided prompts and 3–5 clarifying questions, so highly complex feature planning may require manual expansion of the generated Markdown and YAML artifacts.

Related Skills

Explore More Product & Management Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
hamzaPixlhamzaPixl
2

prd-analysis

Parse PRD files, URLs, or text into structured requirements artifacts.

Community
Advanced
bearbinarybearbinary

prd-to-json

Converts Markdown PRDs into structured JSON task files with progress tracking.

Official
Intermediate
richardnguyen0715richardnguyen0715

deliver-prd

Create Product Requirements Documents using YAML and Markdown templates.

Community
Intermediate