Skip to main content
Prompts PRD and Technical Documentation Generator

general user product template risk: low

PRD and Technical Documentation Generator

Generates comprehensive Product Requirements Documents (PRDs) and technical documentation for specified products or features, structured with sections like introduction, problem st…

PROMPT 

---
name: prd-and-technical-documentation-generator
description: A skill for generating comprehensive Product Requirements Documents (PRDs) and technical documentation for projects.
---

# PRD and Technical Documentation Generator

This skill is designed to assist in the creation of detailed Product Requirements Documents (PRDs) and accompanying technical documentation.

## Instructions

1. **Define the Product or Feature**: Clearly specify the product or feature for which the documentation is being created.
2. **Gather Requirements**: Identify and list all necessary requirements, including functional and non-functional aspects.
3. **Structure the PRD**:
   - **Introduction**: Provide a brief overview of the product or feature.
   - **Problem Statement**: Describe the problem the product or feature aims to solve.
   - **Objectives**: Outline the main goals and objectives.
   - **Scope**: Define the scope, including what is included and excluded.
   - **Requirements**: Detail functional and non-functional requirements.
   - **User Stories**: Include user stories to illustrate usage scenarios.
4. **Technical Documentation**:
   - **Architecture Overview**: Provide an architectural diagram and description.
   - **Technical Specifications**: Detail the technical requirements and specifications.
   - **APIs and Interfaces**: List APIs and interfaces, including usage and examples.
   - **Security and Compliance**: Outline security measures and compliance requirements.

## Examples

- **Example Input**: "Create a PRD for a new e-commerce platform feature"
- **Example Output**: A structured document with all sections populated with relevant information.

## Variables

- ${productFeature} - The specific product feature or initiative.
- ${documentType:PRD} - Type of document to generate (PRD or Technical).

Utilize this skill to efficiently produce comprehensive documentation that supports project objectives and stakeholder needs.

INPUTS

productFeature REQUIRED

The specific product feature or initiative.

e.g. new e-commerce platform feature

documentType

Type of document to generate (PRD or Technical).

e.g. PRD

REQUIRED CONTEXT

  • product or feature description

OPTIONAL CONTEXT

  • document type

ROLES & RULES

  1. Clearly specify the product or feature for which the documentation is being created.
  2. Identify and list all necessary requirements, including functional and non-functional aspects.
  3. Provide a brief overview of the product or feature.
  4. Describe the problem the product or feature aims to solve.
  5. Outline the main goals and objectives.
  6. Define the scope, including what is included and excluded.
  7. Detail functional and non-functional requirements.
  8. Include user stories to illustrate usage scenarios.
  9. Provide an architectural diagram and description.
  10. Detail the technical requirements and specifications.
  11. List APIs and interfaces, including usage and examples.
  12. Outline security measures and compliance requirements.

EXPECTED OUTPUT

Format
structured_report
Schema
markdown_sections · Introduction, Problem Statement, Objectives, Scope, Requirements, User Stories, Architecture Overview, Technical Specifications, APIs and Interfaces, Security and Compliance
Constraints
  • Include PRD sections: Introduction, Problem Statement, Objectives, Scope, Requirements, User Stories
  • Include Technical sections: Architecture Overview, Technical Specifications, APIs and Interfaces, Security and Compliance
  • Structured document format

SUCCESS CRITERIA

  • Generate comprehensive Product Requirements Documents (PRDs)
  • Create accompanying technical documentation
  • Populate all sections with relevant information
  • Support project objectives and stakeholder needs

FAILURE MODES

  • Vague example output description may lead to inconsistent structures.
  • Reliance on unsubstituted variables may result in generic content.
  • Lack of detailed content guidelines may cause hallucinations in specs.

EXAMPLES

Includes one example input and a description of the structured example output.

CAVEATS

Dependencies
  • ${productFeature} variable
  • ${documentType:PRD} variable
  • User input specifying the product or feature
Missing context
  • Precise input format for skill invocation beyond variables.
  • Output format (e.g., Markdown sections, JSON structure).
  • Expected depth/detail level for sections like user stories or architecture diagram.
Ambiguities
  • Does not clarify how documentType variable affects output – e.g., generate only Technical if specified, or always both?
  • Example output is described but not shown concretely.

QUALITY

OVERALL
0.90
CLARITY
0.90
SPECIFICITY
0.80
REUSABILITY
0.95
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Add a full concrete example input-output pair.
  • Clarify documentType handling: 'If documentType=Technical, omit PRD sections.'
  • Specify output as Markdown with headings for each section.
  • Include guidance on generating diagrams (e.g., text-based ASCII or Mermaid).

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR GENERAL USER