Prompt to Prompt: Change Request Planning Template
Prompt to Prompt: Change Request Planning Template is a verified PROMPT blueprint on Promptally in System & Base Contexts optimized for leading AI models. Curated Coding prompt from awesome-prompts library split. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | PROMPT (System & Base Contexts) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 476 |
| Source file | prompt-prompt-change-request-planning-template.txt |
| Access tier | Free public (MIT) |
Pre-Filled Template
### Context
[Why are we doing the change?]
### Desired Behavior
[What is the desired behavior ?]
### Instruction
Explain your comprehension of the requirements.
List 5 hypotheses you would like me to validate.
Create a plan to implement the ${desired_behavior}
### Symbol and action
➕ Add : Represent the creation of a new file
✏️ Edit : Represent the edition of an existing file
❌ Delete : Represent the deletion of an existing file
### Files to be modified
* The list of files list the files you request to add, modify or delete
* Use the ${symbol_and_action} to represent the operation
* Display the ${symbol_and_action} before the file name
* The symbol and the action must always be displayed together.
** For exemple you display “➕ Add : GameModePuzzle.tsx”
** You do NOT display “➕ GameModePuzzle.tsx”
* Display only the file name
** For exemple, display “➕ Add : GameModePuzzle.tsx”
* DO NOT display the path of the file.
** For example, do not display “➕ Add : components/game/GameModePuzzle.tsx”
### Plan
* Identify the name of the plan as a title.
* The title must be in bold.
* Do not precede the name of the plan with "Name :"
* Present your plan as a numbered list.
* Each step title must be in bold.
* Focus on the user functional behavior with the app
* Always use plain English rather than technical terms.
* Strictly avoid writing out function signatures (e.g., myFunction(arg: type): void).
* DO NOT include specific code syntax, function signatures, or variable types in the plan steps.
* When mentioning file names, use bold text.
**After the plan, provide**
* Confidence level (0 to 100%).
* Risk assessment (likelihood of breaking existing features).
* Impacted files (See ${files_to_be_modified})
### Constraints
* DO NOT GENERATE CODE YET.
* Wait for my explicit approval of the plan before generating the actual code changes.
* Designate this plan as the “Current plan”How to use this prompt
- Review the pre-filled example and source files above.
- Copy the template or download
prompt-prompt-change-request-planning-template.txt, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use Prompt to Prompt: Change Request Planning Template?
Open the prompt on Promptally, review the pre-filled example, then copy the template or download prompt-prompt-change-request-planning-template.txt and paste it into your model, IDE or workflow tool. Prompt to Prompt: Change Request Planning Template is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is Prompt to Prompt: Change Request Planning Template free?
Yes. Prompt to Prompt: Change Request Planning Template is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does Prompt to Prompt: Change Request Planning Template need?
Prompt to Prompt: Change Request Planning Template is a static blueprint with no dynamic variables. Copy it and use it as-is.