prd-generation

Generate structured PRDs from Google, Amazon, and Stripe templates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tercel/spec-forge-gemini --skill prd-generation-tercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-generation
Source: https://github.com/tercel/spec-forge-gemini/tree/main/skills/prd-generation
Command: npx skills add https://github.com/tercel/spec-forge-gemini --skill prd-generation-tercel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating consistent, production-ready PRDs is time-consuming and error-prone when teams rely on manual drafting. This skill standardizes PRD creation by combining Google PRD templates, the Amazon Working Backwards narrative, and Stripe Product Specs into a repeatable five-step workflow.

Core Features & Use Cases

  • Five-step PRD generation workflow: Understand Context, Clarify Questions, Launch Document Generation, Content Generation, and Quality Check.
  • Automatic context scanning and alignment with repository templates (references/template.md and references/checklist.md) to ensure consistency with existing docs.
  • Generated PRDs include Mermaid diagrams for user journeys and architecture, with unique IDs following PRD-<MODULE>-NNN.
  • Output is written to docs/<feature-name>/prd.md with revision history and clear formatting.

Quick Start

Provide a feature concept and constraints; the skill will generate a draft PRD aligned to Google PRD, Amazon Working Backwards, and Stripe Product Specs.

Frequently Asked Questions about prd-generation

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

FAQPage Schema
How do I generate a production-ready PRD from a feature idea?

To generate a production-ready PRD, provide your feature concept and constraints. The skill synthesizes Google PRD, Amazon Working Backwards, and Stripe Product Specs templates into a structured document with diagrams and traceability.

What is the workflow for automating PRD creation?

The PRD creation workflow involves five steps: Understand Context, Clarify Questions, Launch Document Generation, Content Generation, and Quality Check. This process ensures your document aligns with repository templates and passes a quality checklist.

Can I include Mermaid diagrams in my product requirements documentation?

Yes, generated PRDs include Mermaid diagrams for user journeys and architecture. These visual diagrams are automatically created during the content generation step to enhance the product requirements documentation.

Does the generated PRD follow a specific naming convention and file structure?

Generated PRDs follow the PRD-<MODULE>-NNN unique ID convention and are written to docs/<feature-name>/prd.md. This ensures consistent file structure, clear formatting, and revision history tracking.

What is the best way to ensure consistency when drafting product requirements across different teams?

Standardizing PRD creation through a repeatable five-step workflow ensures consistency. The skill aligns output with repository templates like references/template.md and references/checklist.md to maintain uniform documentation standards.

Do I need to provide any specific input before launching document generation?

You need to provide a feature concept and any project constraints. The skill automatically scans context and clarifies questions before launching document generation to ensure the PRD meets your requirements.