skills.rest
CasaPerks
CasaPerksOFFICIAL
Explore all skills by this author →
Website𝕏@casaperksGitHub

prd

Generate structured, testable PRDs with audit-ready detail and explicit unknowns (TBD/N/A) for unambiguous engineering specification and hand-off.

Updated Aug 27, 2026
Search Tags:#specification#requirements#acceptance criteria#jira#prd#API-first#product workflow
One-click install
npx skills add https://github.com/CasaPerks/casaflow --skill prd-casaperks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/CasaPerks/casaflow/tree/main/core/skills/prd
Command: npx skills add https://github.com/CasaPerks/casaflow --skill prd-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A PRD turns unclear ideas into structured, testable requirements so reviewers and downstream agents can verify what “done” means before implementation starts.

Core Features & Use Cases

  • Spec-first requirements capture: author an API-first Product Requirements Document that defines the platform contract before UI decisions.
  • Full vs Light PRDs by work type: generate a 12-section Full PRD for features/large improvements or a 5-section Light PRD for bugs/small improvements/tasks.
  • Context-aware drafting and tier refinement: reads Jira context (when available), explores the codebase, optionally scans prior plans, then fills TBD and N/A sections explicitly.
  • Save and (optionally) sync: saves the PRD to the configured vault location and can sync the finalized requirements back to the configured ticket system.

Quick Start

Use /prd to capture requirements for your Jira ticket, choose a Full or Light tier, and produce a complete PRD draft ready for refinement.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write an API-first PRD with enforceable acceptance criteria?▼

Generate a structured PRD by selecting a Full 12-section tier for features or a Light 5-section tier for bugs. The system reads Jira context, explores the codebase, and drafts required sections while explicitly marking unresolved items as TBD or N/A.

How do I create a product requirements document from a Jira ticket?▼

Use the /prd command to capture requirements for your Jira ticket. The system reads available Jira context, selects a Full or Light tier, drafts required sections, and saves the PRD to your configured vault location.

What is the difference between a Full and Light PRD for product workflows?▼

A Full PRD generates a 12-section document for features and large improvements, while a Light PRD generates a 5-section document for bugs, small improvements, and tasks. The system selects the appropriate tier based on your work type.

Do I need Jira context to generate a product requirements document?▼

You do not need Jira context to generate a product requirements document. The system reads Jira context when available, but can also explore the codebase and optionally scan prior plans to draft required sections independently.

How do I sync finalized requirements back to a ticket system?▼

Configure casaflow.config.md settings to sync finalized requirements back to a ticket system. The PRD tool saves the document to your configured vault location and can sync the finalized requirements back to the configured ticket system.

Related Skills

Explore More Product & Management Skills→
andreasphilandreasphil

get-ticket-info

Extract the Jira ticket number from the current branch name and retrieve its description via acli.

Community
Basic
lekmanlekman

refine

Convert rough requirements or Jira tickets into a draft PRD with frontmatter.

Community
Advanced
jnlanahanjnlanahan

prd

Generate a product requirements document from conversation and codebase context.

Community
Intermediate
madebyarismadebyaris
192

sdd-evolve

Update specification files and changelog after implementation discoveries.

Community
Intermediate