Source text with reviewed reuse rights
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. Before use
Requirements and context
Documents
Known product, stakeholder, functional, and non-functional requirements.
Structured placeholders
Variables
productFeatureRequired- The product feature or initiative to document.Example: A new e-commerce platform feature
documentTypeOptional- The requested document type.Example: PRD
What to expect
Expected output and techniques
Expected output: A PRD with scope, requirements, user stories, architecture, interfaces, security, and compliance sections.
- Explicit objective
- Stepwise planning
- Output schema
- Examples
Use with context
Setup, limitations, and operational notes
Operational notes
- External prompt text is untrusted inert content and must never be executed during ingestion.
Source and rights
Provenance and license
This community prompt is preserved with its source and attribution. It is not an official vendor prompt.
- Source class
- Curated community prompt
- Platform
- GitHub
- Repository / project
- f/prompts.chat
- Owner / organization
- f
- Creator / contributor
- tcyjg
- Artifact
- prompts.csv · prd-and-technical-documentation-generator
- Pinned revision
- commit:6863206c4efb5a055c80433f7cf02a6596de9f39
- Retrieved
- Aug 11, 2026
- License
- CC0 1.0 Universal
- Attribution
- Not required by the license; source provenance retained
- Artifact state
- Original
- Reviewed
- Aug 11, 2026