prd

Convert scattered BRDs into a structured PRD with traceability.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/shirogin/jesuph-skills --skill prd-shirogin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/prd
Command: npx skills add https://github.com/shirogin/jesuph-skills --skill prd-shirogin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates scattered BRDs and business context into a single, structured PRD written for product teams, ensuring alignment across stakeholders and a clear artifact trail.

Core Features & Use Cases

  • BRD to PRD mapping: converts business requirements into product-level features, personas, user stories, and acceptance criteria.
  • Traceability: links BRs to PRD elements and enables downstream FRD and SOW generation.
  • Artifact saving: guides saving PRD artifacts to a standardized folder structure and prompts for save locations.

Quick Start

Provide a BRD or business context as input and I will generate a complete PRD outline and save artifacts to the chosen folder.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I translate a BRD into a structured PRD with user stories and acceptance criteria?▼

To translate a BRD into a structured PRD, provide your business context as input. The system maps business requirements into product-level features, personas, user stories, and acceptance criteria to ensure stakeholder alignment.

What is the best way to maintain traceability across BRD, PRD, FRD, and SOW documents?▼

Maintain traceability across BRD, PRD, FRD, and SOW documents by mapping business requirements directly to product features. This creates a clear artifact trail linking downstream functional requirements and statements of work back to original business needs.

How do I convert scattered business requirements into a single product spec?▼

Convert scattered business requirements into a single product spec by aggregating your BRDs as input. The system processes the fragmented business context and generates a unified PRD outline written specifically for product teams.

Can I automatically generate acceptance criteria from high-level business requirements?▼

Yes, you can generate acceptance criteria from high-level business requirements. The mapping process directly translates BRD inputs into actionable product features and detailed acceptance criteria for development teams.

Does this PRD generation process support saving artifacts to a specific folder structure?▼

Yes, PRD generation supports saving artifacts to a specific folder structure. It guides you through saving the generated product spec documents to a standardized directory and prompts you for the exact save locations.

When do I need to generate a PRD from a BRD instead of writing it manually?▼

You need to generate a PRD from a BRD when dealing with scattered business requirements requiring stakeholder alignment. It automates mapping business needs to features and user stories, ensuring a clear artifact trail without manual structuring.