PRD 및 기술 문서 작성

# 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.

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

# PRD 및 기술 문서 생성기

이 지침은 상세한 제품 요구사항 정의서(PRD) 및 관련 기술 문서를 작성하도록 돕습니다.

## 지침

1. **제품 또는 기능 정의**: 문서를 작성할 제품이나 기능을 명확히 지정하세요.
2. **요구사항 수집**: 기능적/비기능적 측면을 포함하여 필요한 모든 요구사항을 파악하고 나열하세요.
3. **PRD 구조화**:
   - **소개**: 제품 또는 기능에 대한 간략한 개요를 제공합니다.
   - **문제 정의**: 제품/기능이 해결하려는 문제를 설명합니다.
   - **목표**: 주요 목표와 목적을 정리합니다.
   - **범위**: 포함되는 사항과 제외되는 사항을 명확히 정의합니다.
   - **요구사항**: 기능 및 비기능 요구사항을 상세히 기술합니다.
   - **유저 스토리**: 사용 시나리오를 설명하는 유저 스토리를 작성합니다.
4. **기술 문서**:
   - **아키텍처 개요**: 아키텍처 구조 설명과 다이어그램 개요를 제공합니다.
   - **기술 사양**: 기술 요구사항 및 명세를 상세히 작성합니다.
   - **API 및 인터페이스**: 사용법 및 예시를 포함한 API 목록을 제공합니다.
   - **보안 및 규정 준수**: 보안 조치 및 규정 준수 요구사항을 나열합니다.

변수:
- ${productFeature} - 특정 제품 기능 또는 이니셔티브
- ${documentType:PRD} - 생성할 문서 유형 (PRD 또는 기술 문서)

• 활용${productFeature} 변수에 구체적인 기획안이나 아이디어를 대입하세요.
• 활용개발 조직과 공유할 기술 사양만 필요하다면 documentType을 'Technical'로 변경하세요.

출처 · prompts.chat · prd-and-technical-documentation-generator — 원문은 출처에 게시된 그대로이며, 권리는 원작자에게 있습니다.

텍스트 결과

Gemini로 실행한 결과입니다. 입력 항목에는 국내 환경의 예시값을 적용했습니다(AI 생성 — 사실 확인 필요).

# 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.

- Eco-friendly Packaging Reward & Payment Feature for Korean Food Delivery App - The specific product feature or initiative.
- PRD - Type of document to generate (PRD or Technical).

개선안

원문과 같은 언어로 보완한 프롬프트입니다. 점수는 명확성 · 구체성 · 출력 형식 · 재사용성 기준의 AI 평가입니다.

# PRD and Technical Documentation Generator

Act as a Principal Product Manager and Solutions Architect. Generate a comprehensive Product Requirements Document (PRD) or Technical Specification based on the inputs provided below.

## Input Parameters
- **Target Item**: [Insert Product/Feature Name or Brief Description]
- **Document Type**: [Select: PRD | Technical Specification | Both]
- **Target Audience**: [e.g., Developers, Stakeholders, Executives]

## Instructions
1. **Analyze Requirements**: Parse the target item to extract core functional, non-functional, and operational needs.
2. **Structure Content**:
   - **Introduction & Problem Statement**: Provide business context, user pain points, and measurable success metrics.
   - **Objectives & Scope**: Define clear in-scope and out-of-scope boundaries.
   - **Requirements & Prioritization**: Detail functional and non-functional requirements categorized by priority (P0/P1/P2).
   - **User Stories**: Write detailed user stories using the format "As a [user], I want [goal] so that [reason]" with acceptance criteria.
   - **Technical Architecture & Specifications**: Outline system components, API endpoints, data models, and security measures (if technical spec is requested).

## Output Format & Constraints
- Use clean Markdown with structured headings, bullet points, and tables where applicable.
- Tone: Professional, unambiguous, and technical.
- Do not leave empty placeholders; fill in realistic details where context is implicit.