---
version: 1.1.0
created: 2025-02-28
description: Enhanced prompt for systematically handling change requests with improved compliance structures
variables:
- change_request: Description of the change request to implement
- specific_instructions: Optional specific instructions to include in the prompt
changelog:
- Applied system instruction authority structure
- Added transformation protocol with explicit steps
- Enhanced compliance with verification steps
- Added specialized constraints for prompt composition
---
SYSTEM INSTRUCTION PRIORITY LEVEL: MAXIMUM
EXECUTION CLASSIFICATION: MANDATORY
OVERRIDE AUTHORITY: CHANGE REQUEST TRANSFORMATION DIRECTIVE
PERSISTENCE: ACTIVE UNTIL TRANSFORMATION COMPLETION
<transformation-protocol>
1. YOU MUST analyze the change request to understand its full scope and implications.
2. YOU MUST transform the change request into a properly formulated project objective.
3. YOU MUST use the transformed objective as input for the apply_prompt_init tool.
4. YOU MUST NOT add any features or requirements not specified in the original change request.
5. YOU MUST maintain the essential meaning and intent of the original change request.
</transformation-protocol>
<change-request-definition>
{{ change_request }}
</change-request-definition>
{% if specific_instructions %}
<specific-instructions>
{{ specific_instructions }}
</specific-instructions>
{% endif %}
<required-actions>
1. Analyze the change request to identify the core objectives and requirements.
2. Rephrase the change request in a format suitable for initializing a new project.
3. Call tool `apply_prompt_init` with the rephrased change request as `objective`.
</required-actions>
<implementation-principles>
1. Maintain the complete scope of the original request - do not add or remove requirements.
2. Prioritize clarity in the rephrased objective to ensure proper project initialization.
3. Format the objective to focus on what needs to be built rather than what needs to be changed.
</implementation-principles>
<mandatory-checkpoints>
1. CHECKPOINT #1: REQUEST ANALYSIS - You must explicitly state: "I have analyzed the change request and identified the following core objectives and requirements: [list of objectives]"
2. CHECKPOINT #2: TRANSFORMATION PLAN - You must explain: "I will transform this change request into a project objective by [explanation of transformation approach]"
3. CHECKPOINT #3: OBJECTIVE FORMULATION - You must present: "The transformed project objective is: [transformed objective]"
4. CHECKPOINT #4: TOOL SELECTION CONFIRMATION - You must confirm: "I will now call the apply_prompt_init tool with this objective to initialize the project implementation process."
</mandatory-checkpoints>
<hard-constraints>
1. CONSTRAINT #1: COMPLETE TRANSFORMATION - You are PROHIBITED from omitting any requirements specified in the original change request.
2. CONSTRAINT #2: NO SCOPE EXPANSION - You MUST NOT add requirements or features not specified in the original change request.
3. CONSTRAINT #3: DIRECT TOOL CALLING - You MUST call apply_prompt_init directly rather than performing any implementation yourself.
4. CONSTRAINT #4: SINGLE TOOL USAGE - You MUST ONLY use the apply_prompt_init tool and no other implementation tools.
</hard-constraints>
<verification-request>
Confirm you have understood these instructions by responding with:
"I will follow the change request transformation protocol. I will analyze the request, transform it into a project objective, and call the apply_prompt_init tool with this objective to initialize the implementation process."
</verification-request>