Present
Contributed by ms.seyer@gmail.com
Improved by Laravel Company · 2026-09-07
Context
[Why are we implementing this feature? Please provide a clear business reason and describe the current pain points or limitations in the existing functionality.]
Desired Behavior
[Describe the intended user experience and functional requirements in detail. What specific actions should the user be able to perform? What are the expected results? Consider edge cases and error handling.]
Instruction
Demonstrate your deep understanding of the requirements by explaining them in your own words. Your explanation should be concise yet comprehensive, covering all essential aspects.
Generate a list of 5-7 hypotheses or assumptions you believe are necessary to implement this feature successfully. These hypotheses should be specific, testable, and cover potential challenges or unknowns in the current system.
Create a high-level implementation plan that outlines the key steps required to achieve the desired behavior. Your plan should:
- Have a clear, descriptive title that sums up the purpose of the feature.
- Be presented as a numbered list, with each step clearly labeled.
- Focus on the user's interaction with the application and the intended functionality.
- Avoid technical jargon and stick to plain English.
- Do not include specific code syntax, function signatures, or variable types.
- Use bold text for file names when mentioning them in the plan steps.
Symbol and Action
â Add : Represents the creation of a new file
âï¸ Edit : Represents the modification of an existing file
â Delete : Represents the removal of an existing file
Files to Be Modified
- List all the files you propose to add, modify, or delete to implement the feature.
- Use the ${symbol_and_action} before the file name to represent the operation.
- Only include the file name, without the path. For example, display "â Add : GameModePuzzle.tsx" instead of "â Add : components/game/GameModePuzzle.tsx".
- Ensure the symbol and action are displayed together as a unit.
Plan Format
Title of the Plan
Step 1 Title
- Description of the step in plain English
- Any specific details about the step
Step 2 Title
- Description of the step in plain English
- Any specific details about the step
...
After the Plan
- Indicate your confidence level in the plan's completeness and feasibility on a scale of 0-100%.
- Assess the likelihood of the plan breaking existing functionality and causing issues for users.
- Identify which files are expected to be modified according to the ${files_to_be_modified} format provided.
Constraints
- Do not proceed to generate the actual code yet. This plan must be approved by me before any code changes are made.
- Designate this plan as the "Current plan".
Please provide the plan and ensure it adheres to the format and guidelines specified above. The plan should be clear, concise, and easy to understand for both technical and non-technical stakeholders.
Original prompt (before our improvements)
### 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”