External Release Document Template
설명
This prompt allows users to create a comprehensive external release document for a given prompt. The document includes sections such as title and objective, prompt details, use case scenarios, testing and validation, feedback and insights, and final recommendations. The purpose is to analyze the prompt, summarize its core purpose, identify the target audience, and describe its primary use case. The template guides users through providing detailed descriptions, example inputs and outputs, testing methodologies, and practical advice for implementation.
워크플로우
Input
Please provide the complete prompt text to be analyzed.-Please provide the complete prompt text to be analyzed.
Please provide any additional information such as testing details, models used, system instructions, and other relevant context. If there is no additional info, type '.'.-Please provide any additional information such as testing details, models used, system instructions, and other relevant context. If there is no additional info, type '.'.
1. External Release Document Template
모델: Gemini-2.5 Pro
프롬프트:
## Input Values
1. prompt - The complete prompt text to be analyzed
2. additional_info - Testing details, models used, system instructions, and other relevant context (optional) // If there's no additional info, you need to type '.'
## Output Template
### 1. Title and Objective
- **Title:** [Generate an attractive, self-explanatory title that highlights the "wow" factor of the prompt]
- **Objective:**
- [Analyze the prompt to summarize its core purpose]
- [Identify and describe the target audience and primary use case]
### 2. Prompt Details
- **Description:**
- [Analyze and explain the prompt structure and purpose]
- [Break down key components and their functions]
- **Inputs:**
- Example 1: [Create an example input based on prompt analysis]
- Example 2: [Create another example input showing a different use case]
- **Outputs:**
- Example 1: [Expected output for Example 1]
- Example 2: [Expected output for Example 2]
- **Time Expectation:**
- Pages processed: [Based on prompt analysis and additional info]
- Execution time: [Based on provided testing data or prompt complexity]
### 3. Use Case Scenarios
- **Primary Use Cases:**
- Scenario 1: [Describe a practical application]
- Scenario 2: [Describe an alternative application]
- [Additional scenarios if evident from prompt structure]
### 4. Testing and Validation
[Note: Include only one of these versions in the final document based on available information]
- Version A - When testing data is provided:
Methodology:
[Describe testing approach used]
[Explain test conditions]
Results:
Performance metrics: [From provided data]
Key findings: [Analysis of test results]
- Version B - When no testing data is provided:
Recommended Testing Approach:
[Suggest testing methodology based on prompt purpose]
[Outline key metrics to track]
[Note: Delete this instruction block and the unused version in the final document]
### 5. Feedback and Insights
- **Strengths:**
- [Analyze prompt to identify key advantages]
- [Highlight unique features or capabilities]
- **Areas for Consideration:**
- [Note important factors for optimal use]
- [Identify scenarios where additional review may be needed]
### 6. Final Recommendations
- **Implementation Guidelines:**
- [Provide practical advice for using the prompt]
- [List best practices based on analysis]
- **Adoption Criteria:**
- [Specify ideal use conditions]
- [Outline requirements for successful implementation]
=========================================
## Document Preparation Instructions:
1. Analyze the provided **prompt** thoroughly
2. Review any **additional_info** provided
3. Complete each section based on the analysis
4. Ensure all examples are relevant and practical
5. Verify that recommendations align with prompt capabilities
6. Remove any sections that cannot be substantively completed based on available inputs
## Note:
- Each section should be completed based on careful analysis of the prompt and any provided additional information.
- If certain aspects cannot be determined from the inputs, focus on providing actionable insights based on what is known rather than speculation.
- IMPORTANT: do not add any additional comments other than items delineated in the output template structure.
1. prompt - The complete prompt text to be analyzed
2. additional_info - Testing details, models used, system instructions, and other relevant context (optional) // If there's no additional info, you need to type '.'
## Output Template
### 1. Title and Objective
- **Title:** [Generate an attractive, self-explanatory title that highlights the "wow" factor of the prompt]
- **Objective:**
- [Analyze the prompt to summarize its core purpose]
- [Identify and describe the target audience and primary use case]
### 2. Prompt Details
- **Description:**
- [Analyze and explain the prompt structure and purpose]
- [Break down key components and their functions]
- **Inputs:**
- Example 1: [Create an example input based on prompt analysis]
- Example 2: [Create another example input showing a different use case]
- **Outputs:**
- Example 1: [Expected output for Example 1]
- Example 2: [Expected output for Example 2]
- **Time Expectation:**
- Pages processed: [Based on prompt analysis and additional info]
- Execution time: [Based on provided testing data or prompt complexity]
### 3. Use Case Scenarios
- **Primary Use Cases:**
- Scenario 1: [Describe a practical application]
- Scenario 2: [Describe an alternative application]
- [Additional scenarios if evident from prompt structure]
### 4. Testing and Validation
[Note: Include only one of these versions in the final document based on available information]
- Version A - When testing data is provided:
Methodology:
[Describe testing approach used]
[Explain test conditions]
Results:
Performance metrics: [From provided data]
Key findings: [Analysis of test results]
- Version B - When no testing data is provided:
Recommended Testing Approach:
[Suggest testing methodology based on prompt purpose]
[Outline key metrics to track]
[Note: Delete this instruction block and the unused version in the final document]
### 5. Feedback and Insights
- **Strengths:**
- [Analyze prompt to identify key advantages]
- [Highlight unique features or capabilities]
- **Areas for Consideration:**
- [Note important factors for optimal use]
- [Identify scenarios where additional review may be needed]
### 6. Final Recommendations
- **Implementation Guidelines:**
- [Provide practical advice for using the prompt]
- [List best practices based on analysis]
- **Adoption Criteria:**
- [Specify ideal use conditions]
- [Outline requirements for successful implementation]
=========================================
## Document Preparation Instructions:
1. Analyze the provided **prompt** thoroughly
2. Review any **additional_info** provided
3. Complete each section based on the analysis
4. Ensure all examples are relevant and practical
5. Verify that recommendations align with prompt capabilities
6. Remove any sections that cannot be substantively completed based on available inputs
## Note:
- Each section should be completed based on careful analysis of the prompt and any provided additional information.
- If certain aspects cannot be determined from the inputs, focus on providing actionable insights based on what is known rather than speculation.
- IMPORTANT: do not add any additional comments other than items delineated in the output template structure.
Output:
1: External Release Document TemplateExternal Release Document Template
정보
만든 사람: Sung Lee
6
실행 수
1
즐겨찾기
9.8s
평균 실행 시간
$0.04
평균 실행 비용
활용 예시 (0)