sdd-prd

Invoke this Skill with the sdd-pm agent and it guides you through 13 collaborative steps: context gathering, project classification, vision discovery, success criteria, user journeys, scoping, and functional and non-functional requirements. Each section is drafted, refined with you, and appended to prd.md.

The Edit PRD Workflow loads your existing prd.md, detects its format, audits it against quality standards, and builds a prioritized change plan. After your approval, it applies edits section by section and verifies the final document.

Functional requirements use the format 'FR#: [Actor] can [capability] [context/constraint]', targeting 20-50 requirements organized into 5-8 capability areas. They describe what capability exists, never how to implement it, keeping them testable and readable by designers and architects.

Yes, the workflow detects greenfield versus brownfield contexts during project discovery and adapts accordingly. It reads existing project docs like README and package.json for brownfield projects, or gathers context directly from the user for greenfield products.

Do not use it for architecture decisions, UX design, or implementing features, as those belong to downstream skills like architecture and UX document workflows. The PRD defines what the product is and why, not how to build it.