rcode-create-prd

Create a complete product requirements document through guided discovery and structured drafting.

2|1|Updated Apr 10, 2026

Search Tags:#discovery #functional requirements #prd #product requirements #non-functional requirements #scope planning #document polish

Ready to run

npx skills add https://github.com/hanzlahabib/rcode --skill rcode-create-prd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rcode-create-prd
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/2-plan/rcode-create-prd
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-create-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create a complete product requirements document from scratch through structured discovery instead of starting with a blank template.

Core Features & Use Cases

It guides collaborative PRD creation across classification, vision, success criteria, user journeys, scope, functional requirements, non-functional requirements, and final polish. It is designed for new product specs, feature planning, and brownfield change requests where precise, measurable requirements are needed for downstream design and engineering. It enforces dense, testable, traceable output with explicit owners, deadlines, scope boundaries, and polished document structure.

Quick Start

Ask this skill to create a PRD for your product by naming the feature, the target users, and the problem you want to solve.

Frequently Asked Questions about rcode-create-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a product requirements document from scratch without a template?▼

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.

What is the best way to write functional and non-functional requirements for a new feature?▼

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.

How do I structure a PRD for a brownfield change request?▼

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.

Does guided PRD discovery work for both new product proposals and feature planning?▼

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.

How do I ensure my PRD has measurable and traceable requirements?▼

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.

What should I include in a PRD scope planning section?▼

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.