Simon/awesome-chatgpt-prompts
1
0
Fork 0
mirror of https://github.com/f/awesome-chatgpt-prompts.git synced 2026-04-18 12:10:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add prompt: prd-and-technical-documentation-generator

Browse Source
This commit is contained in:
tcyjg
2026-04-15 04:05:09 +00:00
parent f6a56a61be
commit 41927597f0
2 changed files with 86 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
PROMPTS.md
View File

@@ -117472,3 +117472,52 @@ Strong success criteria let you loop independently. Weak criteria ("make it work
</details>
<details>
<summary><strong>prd-and-technical-documentation-generator</strong></summary>
## prd-and-technical-documentation-generator
Contributed by [@tcyjg](https://github.com/tcyjg)
```md
---
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.
```
</details>

37
prompts.csv
View File

@@ -97474,3 +97474,40 @@ Transform tasks into verifiable goals:
For multi-step tasks, state a brief plan:
\
Strong success criteria let you loop independently. Weak criteria (""make it work"") require constant clarification.",FALSE,TEXT,yazz4444
prd-and-technical-documentation-generator,"---
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.",FALSE,TEXT,tcyjg
Can't render this file because it is too large.