pdd-ba

Name: pdd-ba
Availability: InStock
Author: wonderslife

Analyze PRD requirements using 5W1H, MECE, and CRUD to generate business analysis reports.

13|3|Updated Apr 7, 2026

Search Tags:#prd #business-analysis #use-cases #mece #5w1h #process-diagrams #crd-matrix

Ready to run

npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-ba

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pdd-ba
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/core/pdd-ba
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-ba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps analysts convert PRDs and business requirements into structured, actionable artifacts using established methodologies (5W1H, MECE, CRUD), enabling consistent interpretation, scoping, and feature extraction across teams.

Core Features & Use Cases

5W1H analysis for each requirement to clarify Why, What, Who, When, Where, and How
MECE principle to ensure complete, non-overlapping feature sets
Business modeling artifacts: Use Case diagrams, Process flows, State diagrams, and CRUD matrices
Business rule extraction with risk and assumption tracking
Output generation: comprehensive Business Analysis Report, glossary, and alignment with PRD sections

Quick Start

Submit the PRD or business requirements text to generate a complete business analysis report.

Frequently Asked Questions about pdd-ba

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

FAQPage Schema

How do I convert a PRD into a structured business analysis report?▼

To convert a PRD into a business analysis report, submit the requirements text to apply 5W1H and MECE methodologies. The process extracts business rules and generates structured artifacts like use-case diagrams, CRUD matrices, and a glossary, ensuring all conclusions trace back to the source document.

What is the best way to ensure my business requirements are complete and non-overlapping?▼

The best way to ensure business requirements are complete and non-overlapping is to apply the MECE principle. This structures the feature sets exhaustively while eliminating overlaps, producing a consistent scope and a rules catalog aligned with the PRD.

Can I generate CRUD matrices and process diagrams directly from business rules?▼

Yes, you can generate CRUD matrices and process diagrams directly from business rules. By submitting stakeholder notes and process descriptions, the analysis outputs visual artifacts like state diagrams and CRUD matrices alongside risk and assumption tracking sections.

How does 5W1H analysis clarify stakeholder notes for feature extraction?▼

5W1H analysis clarifies stakeholder notes by systematically breaking down each requirement into Who, What, Where, When, Why, and How. This structured interrogation ensures consistent interpretation and precise scoping for feature extraction across teams.

Do I need a fully written PRD to generate use-case diagrams and state diagrams?▼

No, a fully written PRD is not strictly required to generate use-case diagrams and state diagrams. You can submit available process descriptions, business rules, or stakeholder notes to produce the visual artifacts and comprehensive analysis outputs.

Why should I include risk and assumption sections when analyzing PRD requirements?▼

Including risk and assumption sections when analyzing PRD requirements ensures that potential gaps and dependencies are explicitly tracked. This contextualizes the generated CRUD matrices and business models, providing traceable support for all extracted conclusions.