structure updates
This commit is contained in:
@@ -0,0 +1,46 @@
|
||||
## MISSION or GOAL
|
||||
- **Define Clear Objective**: Start with a concise statement of the primary goal or purpose of the instructions.
|
||||
|
||||
## INPUT SPECIFICATION
|
||||
- **Input Description**: Briefly describe the types of input the instructions pertain to (user queries, operational commands, etc.).
|
||||
|
||||
## STEP-BY-STEP PROCEDURE
|
||||
- **Enumerate Actions**: List the actions or steps in a logical, clear order. Keep each step simple and direct.
|
||||
|
||||
## EXPECTED OUTCOME
|
||||
- **Outcome Specification**: Clearly state the intended result or outcome of following these instructions.
|
||||
|
||||
## HANDLING VARIABILITY
|
||||
- **Variation Guidelines**: Provide guidelines on how to handle different scenarios or exceptions that may arise.
|
||||
|
||||
## EFFICIENCY TIPS
|
||||
- **Optimization Advice**: Offer quick tips for efficient execution or highlight common mistakes to avoid.
|
||||
|
||||
## CONTINUOUS IMPROVEMENT
|
||||
- **Feedback and Refinement**: Suggest ways to incorporate feedback for ongoing improvement of the process.
|
||||
|
||||
### Example Template
|
||||
|
||||
#### MISSION
|
||||
Simplify User Interaction
|
||||
|
||||
#### INPUT SPECIFICATION
|
||||
User requests in a customer service context.
|
||||
|
||||
#### STEP-BY-STEP PROCEDURE
|
||||
1. Greet the user.
|
||||
2. Identify the request.
|
||||
3. Provide a direct solution.
|
||||
4. Offer further assistance.
|
||||
|
||||
#### EXPECTED OUTCOME
|
||||
User’s issue resolved in minimal interactions.
|
||||
|
||||
#### HANDLING VARIABILITY
|
||||
For unclear requests, prompt for specific details.
|
||||
|
||||
#### EFFICIENCY TIPS
|
||||
Use user-friendly language and confirm understanding.
|
||||
|
||||
#### CONTINUOUS IMPROVEMENT
|
||||
Regularly update FAQs based on frequent user queries.
|
||||
Reference in New Issue
Block a user