Generate standardized PRD documents with schema validation and traceability templates.
npx skills add https://github.com/jrlangford/ddd-companion --skill ddd-prd
Please help me install this Agent Skill. Skill: ddd-prd Source: https://github.com/jrlangford/ddd-companion/tree/main/skills/ddd-prd Command: npx skills add https://github.com/jrlangford/ddd-companion --skill ddd-prd
PRDs are often created inconsistently and can take significant time to structure; this skill provides a reusable PRD schema, built-in validation, and templates to standardize the artifacts and accelerate downstream DDD activities.
Use /ddd-prd template to generate a blank PRD for a new project.
High-intent search queries and answers about installing and using this skill.
A PRD schema standardizes document creation by enforcing a consistent structure with sections like Executive Summary, Domain Glossary, and Business Rules. This ensures completeness and traceability for teams practicing Domain-Driven Design workflows.
A PRD for bounded context analysis should include sections like Conceptual Entities, Domain Glossary, Business Rules, and Integration Touchpoints. These structured sections provide the necessary domain vocabulary to seed bounded context design.
You validate PRD completeness and traceability by applying built-in validation utilities against a formal schema to check conformance. This ensures all structured sections meet requirements before seeding downstream DDD artifact generation.
Yes, you can generate a blank PRD template to standardize requirements across projects. A reusable template enforces a consistent structure covering Success Criteria, Non-Functional Requirements, and a Traceability Index for every team.
Yes, DDD PRD generation supports a Role-Capability Matrix within its structured sections to map functional areas against user roles. This ensures clear capability allocation and end-to-end traceability from requirements to design.
kryptonum-devGenerate schema-conformant PRD markdown from shaped input notes.
nandinhosGenerate a domain-model.json with entities, bounded contexts, and invariants.
EnigmaWUDefine bounded contexts and map integration contracts for domain-driven design.
matiaspakuaTranslate business requirements into functional specifications, use cases, and data-flow diagrams.
