skills.rest
Kuass
KuassCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd

Generate structured Product Requirements Documents with acceptance criteria and machine-convertible tasks.

1|Updated Mar 4, 2026
Search Tags:#documentation#specification#acceptance criteria#feature planning#prd#product requirements
One-click install
npx skills add https://github.com/Kuass/kiro-gateway-plus --skill prd-kuass
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Kuass/kiro-gateway-plus/tree/main/.opencode/skill/prd
Command: npx skills add https://github.com/Kuass/kiro-gateway-plus --skill prd-kuass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs) to clearly define the desired end-state of a feature, ensuring alignment among stakeholders before development begins.

Core Features & Use Cases

  • Structured PRD Generation: Creates PRDs following a defined template, suitable for RFC review.
  • Acceptance Criteria: Includes clear WHEN/THEN scenarios and machine-convertible tasks with metadata.
  • Use Case: When planning a new user authentication flow, use this skill to generate a PRD that details the user experience, security requirements, and defines acceptance criteria for a successful implementation.

Quick Start

Use the prd skill to create a new product requirements document for the upcoming user profile redesign.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a Product Requirements Document for a new feature?▼

This skill generates a structured Product Requirements Document that defines the end-state of a feature, including acceptance criteria and machine-convertible tasks.

What should be included in acceptance criteria for feature planning?▼

Acceptance criteria should include clear WHEN/THEN scenarios and machine-convertible tasks with metadata, ensuring alignment among stakeholders before development begins.

Can I use this PRD skill for planning migrations or refactors?▼

Yes, this skill supports planning new features, migrations, or refactors by clarifying WHAT to build and WHY, not HOW or WHEN.

Does the PRD generation include machine-convertible tasks?▼

Yes, PRD generation includes machine-convertible tasks with metadata and integrates with a bead ID system for artifact management.

What is the difference between defining end-state and HOW to build it?▼

Defining the end-state specifies WHAT to build and WHY for stakeholder alignment, whereas HOW to build it involves technical implementation details not covered in the PRD.

When do I need a structured PRD for RFC review?▼

You need a structured PRD for RFC review when planning a new feature, such as a user authentication flow, to detail user experience and security requirements before implementation.

Related Skills

Explore More Product & Management Skills→
lluppesmslluppesms

breakdown-feature-prd

Generate structured Markdown PRDs from Epic feature descriptions.

Community
Intermediate
KuassKuass
1

prd-task

Convert Markdown PRDs into executable JSON task lists.

Community
Intermediate
hgflimahgflima
1

spec-driven-development

Create detailed specifications, technical plans, and task breakdowns for software projects.

Community
Advanced
fkbertholdfkberthold

feature-a-bead

Coordinate feature-bead work with contract-driven variable middle and lifecycle scaffolding.

Community
Advanced