Analyze PRD requirements using 5W1H, MECE, and CRUD to generate business analysis reports.
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-ba
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
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.
Submit the PRD or business requirements text to generate a complete business analysis report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
DergaczGenerate schema-conformant Product Requirement Documents from shaped or raw notes.
VSF-QC-TTSGenerate and structure Business Requirements Documents from YAML metadata and regex patterns.
atanakaGenerate PlantUML sequence diagrams from use-case specifications and domain models.
OzeroHAXAnalyze documentation and code to extract business rules and process flows.
