cria-prd

Create standardized PRDs from feature requests in the project tasks directory.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/leonanpereirapinto/ai-utils --skill cria-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cria-prd
Source: https://github.com/leonanpereirapinto/ai-utils/tree/main/skills/spec-driven/cria-prd
Command: npx skills add https://github.com/leonanpereirapinto/ai-utils --skill cria-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Creates Product Requirements Documents (PRDs) from feature requests following a structured workflow of clarification, planning, and drafting. Outputs a standardized PRD to the project tasks directory. Use when the user asks to create a PRD, define requirements, or document a new feature. Do not use for technical specifications, task breakdowns, or implementation planning.

Core Features & Use Cases

  • Clarification-driven PRD drafting: guides users through gathering problem statements, user stories, scope, and success criteria.
  • Standardized output: saves PRD to ./tasks/prd-[feature-slug]/prd.md, ensuring a consistent template.
  • Non-technical focus: excludes implementation details and technical specs to keep the PRD focused on outcomes and constraints.

Quick Start

Provide the feature name and brief description; I will generate a PRD at ./tasks/prd-[feature-slug]/prd.md.

Frequently Asked Questions about cria-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 request?

To create a product requirements document from a feature request, provide the feature name and brief description to trigger a clarification, planning, and drafting workflow that outputs a standardized PRD.

What is the best way to structure a PRD for non-technical stakeholders?

The best way to structure a PRD for non-technical stakeholders is using a frontmatter-driven template that captures problem statements, user stories, scope, and success criteria while explicitly excluding technical specifications.

How do I define functional requirements and success criteria for a new feature?

You define functional requirements and success criteria for a new feature by following a guided clarification workflow that prompts you for problem statements, user stories, and scope, resulting in numbered functional requirements.

Can I use this workflow to generate technical specifications and task breakdowns?

No, you cannot use this workflow to generate technical specifications or task breakdowns. The PRD drafting process focuses strictly on outcomes and constraints, excluding implementation details and technical specs.

Where are generated PRDs saved when documenting product requirements?

Generated PRDs are saved as standardized markdown files in the project tasks directory at the path ./tasks/prd-[feature-slug]/prd.md, ensuring consistent template output and file organization.