rcode-create-prd

Create a product requirements document through guided discovery by naming the feature, target users, and problem to solve. The skill captures vision, success criteria, scope, and functional requirements step by step instead of starting with a blank template.

The best way to write functional and non-functional requirements is through stepwise capture during guided discovery. This enforces dense, testable, traceable output with explicit owners, deadlines, and scope boundaries for downstream design and engineering teams.

Structure a PRD for a brownfield change request by applying guided discovery to capture classification, vision, success criteria, journeys, scope, and requirements. This produces precise, measurable requirements needed for downstream design and engineering changes.

Guided PRD discovery works for new product proposals, feature planning, and brownfield change requests. It supports stepwise capture of vision, success criteria, journeys, scope, functional and non-functional requirements, frontmatter state, and final document polish across all these contexts.

Ensure measurable and traceable requirements by using guided discovery to enforce dense, testable output with explicit owners, deadlines, and scope boundaries. The structured drafting process captures success criteria and functional requirements that downstream teams can verify and review.

Include vision, success criteria, user journeys, scope boundaries, functional and non-functional requirements, and frontmatter state in your PRD scope planning. Guided discovery captures each element stepwise and applies final document polish for a complete, reviewable product spec.