## PURPOSE
-   Define **Core Objective**: State the primary goal or purpose of these instructions.
-   Explain **Impact**: Briefly describe the significance or benefit of achieving this objective.

---

## INPUTS
-   **Description**: Briefly outline the types of information or resources these instructions require (e.g., user queries, system data).
-   **Required Details**: Specify any particular data, files, or specific starting conditions needed.

---

## PREREQUISITES
-   **Pre-conditions**: List any essential prior knowledge, necessary tools, or required permissions before starting.

---

## PROCEDURE
-   **Step-by-Step Actions**: Enumerate all actions in a logical, clear, and direct order. Keep each step concise.
-   **Clarity Aids (Optional)**: Suggest incorporating visuals (e.g., screenshots, diagrams) or concrete examples for complex steps.

---

## OUTCOME
-   **Desired Result**: Clearly state the intended result of successfully following these instructions.
-   **Success Criteria**: Where applicable, define how success will be measured (e.g., specific output, completion status, user satisfaction).

---

## VARIATIONS & EXCEPTIONS
-   **Handling Guidelines**: Provide instructions for managing different scenarios, common exceptions, or minor deviations.
-   **Escalation Path**: Specify who to contact or what team to involve for issues that cannot be resolved using these guidelines.

---

## EFFICIENCY TIPS
-   **Optimization Advice**: Offer quick tips for more efficient execution or highlight common pitfalls to avoid.

---

## FEEDBACK & IMPROVEMENT
-   **Refinement Process**: Suggest methods for gathering feedback and ensuring continuous improvement of the instructions.
-   **Version Control**: Recommend a system for tracking changes and updates to the document.

---

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