product-document

Create a canonical Product Requirements Document from a rough product idea.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill product-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-document
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/product-document
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill product-document

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Turns a rough product idea into a structured, project-level Product Requirements Document (PRD) that can be registered as the canonical specs/prd.md for consistent discovery and governance.

Core Features & Use Cases

  • Generate and register a canonical PRD at specs/prd.md from a rough product idea.
  • Preserve and graft existing narrative sections while updating the PRD baseline.
  • Read optional project configuration to align with the registered workflow and downstream processes.

Quick Start

Describe your product idea and run this Skill to produce the canonical PRD at specs/prd.md.

Frequently Asked Questions about product-document

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

FAQPage Schema
How do I turn a rough product idea into a structured PRD?

You can generate a canonical PRD by providing a rough product idea, which the system then structures into a formal document registered at specs/prd.md to align with your project workflow.

What is the canonical specs/prd.md file used for in project governance?

Used in project governance, specs/prd.md acts as the canonical product requirements document, preserving narrative sections while updating the baseline for downstream processes.

Can I preserve existing narrative sections when updating a Product Requirements Document?

Yes, the PRD generation process preserves and grafts existing narrative sections into the newly generated document, maintaining your project context baseline while enforcing structured updates.

Does generating a PRD require specific project configuration?

No specific configuration is required to start, though the tool reads optional project configuration to align the generated PRD with your registered workflow and downstream planning processes.

How does PRD generation apply to system-design and product discovery workflows?

It integrates into product discovery and system-design workflows by transforming rough ideas into a canonical PRD, which then updates the project context baseline for downstream planning and governance.

What is the best way to register a product requirements document for downstream planning?

Registering your product requirements document as specs/prd.md establishes a canonical baseline that aligns with project configuration and feeds directly into downstream planning and governance workflows.