{"enrichment":{"faq":[{"a":"doc-prd translates your Business Requirements Document into a structured Product Requirements Document by mapping BRD goals to product features, user personas, and success metrics. The skill guides you through defining container-level capabilities and acceptance criteria that bridge upstream business intent with downstream EARS specifications, maintaining full traceability across the SDD workflow.","q":"How do I write a PRD from a BRD?"},{"a":"doc-prd structures PRD content around customer personas, product features, user journeys, and measurable success criteria (KPIs). It helps you author customer-facing messaging alongside technical requirements, ensuring personas are tied to specific capabilities and success metrics validate that features deliver business value.","q":"What should a doc-prd include for personas and success metrics?"},{"a":"doc-prd defines product capabilities and user requirements at the container level\u2014the intermediate abstraction between high-level business goals and detailed EARS specifications. This layer captures what the product must do and for whom, without prescribing implementation details, making it the ideal staging point for architectural elaboration and downstream requirement decomposition.","q":"What is the product container level requirements in doc-prd?"},{"a":"doc-prd operates as Layer 2 of the SDD workflow, positioned between upstream BRD and downstream EARS, BDD, and ADR artifacts. It validates traceability by ensuring every business requirement maps to product features and acceptance criteria, and every feature can be traced forward into detailed specifications and architectural decisions.","q":"How does doc-prd fit into the SDD workflow?"},{"a":"Yes. doc-prd translates architectural topics from the BRD into technical evaluation options suitable for Architecture Decision Records. It structures these elaborations within the PRD so downstream ADR authors have clear context, trade-offs, and constraints to inform their architectural choices.","q":"Can doc-prd help elaborate architectural topics for ADR decisions?"},{"a":"doc-prd offers section templates and guidance for creating a complete PRD: business context, personas, features, user journeys, acceptance criteria, success metrics, and architectural considerations. Each section includes best practices for maintaining clarity and traceability, helping you produce a professional, actionable PRD that stakeholders and engineers can follow.","q":"What PRD document structure and templates does doc-prd provide?"}],"shadow_tags":["requirements-authoring","product-specification","container-level-design","workflow-artifact","upstream-translation","feature-definition","stakeholder-alignment","acceptance-criteria","documentation-framework","traceability-chain"],"summary_rewrite":"doc-prd generates a Product Requirements Document as Layer 2 of the SDD workflow, converting business requirements into product capabilities, user personas, and measurable success criteria. It structures features and acceptance criteria at the container level, sitting between upstream BRD and downstream EARS artifacts."},"files":[{"bytes":9772,"path":"platforms/claude-code-plugin/skills/doc-prd/SKILL.md","sha256":"7deba9aa194238be7688b8fcc52637b81444a47cf39d435769f1581102d94895","url":"https://skillfed.io/files/vladm3105/aidoc-flow-framework/doc-prd/451aae82/SKILL.md"}],"id":"vladm3105/aidoc-flow-framework/doc-prd","links":{"html":"https://skillfed.io/vladm3105/aidoc-flow-framework/doc-prd","md":"https://skillfed.io/vladm3105/aidoc-flow-framework/doc-prd.md","repo":"https://github.com/vladm3105/aidoc-flow-framework"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":3,"language":"Python","last_updated":"2026-07-27","license":"MIT","name":"doc-prd","publisher":"vladm3105","stars":16},"relations":{"categories":["product-management","requirements-engineering","documentation-framework"],"similar":[{"id":"vladm3105/aidoc-flow-framework/doc-prd-autopilot"},{"id":"vladm3105/aidoc-flow-framework/doc-prd-fixer"},{"id":"vladm3105/aidoc-flow-framework/doc-prd-audit"},{"id":"vladm3105/aidoc-flow-framework/doc-brd"},{"id":"vladm3105/aidoc-flow-framework/doc-flow"},{"id":"vladm3105/aidoc-flow-framework/doc-tdd"},{"id":"vladm3105/aidoc-flow-framework/sdd-orchestrator"},{"id":"vladm3105/aidoc-flow-framework/doc-adr"},{"id":"vladm3105/aidoc-flow-framework/doc-ears"},{"id":"vladm3105/aidoc-flow-framework/doc-bdd"}]},"slug":{"owner":"vladm3105","repo":"aidoc-flow-framework","skill":"doc-prd"},"version":"451aae82"}