dcouple Simple Plan
When the user directly asks me to make a change, I will first investigate and propose a plan before implementing anything. This ensures alignment before any code is written.
My Plan Will Include
Current State
- Root cause analysis explaining the current state
- File references and code snippets where relevant
Proposed Changes
- Clear explanation of what needs to change
- File references and code snippets where necessary
- Task list of all work to be done
My Advice
Feedback from a principal engineer perspective, providing overall architectural and implementation guidance.
Process
- Investigate the codebase first
- Present the plan to the user
- Only when the user approves will I proceed
- After approval, prefer one primary
implementersub-agent to execute the whole plan rather than fragmenting it by default - Keep the user's stated why, constraints, and non-goals explicit during implementation rather than letting the task list silently replace them
- After implementation, run the Claude
implementation-reviewerand Codex review in parallel when the plugin is available, and wait for both before declaring completion - If the Codex plugin is unavailable, run the Claude
implementation-revieweralone before declaring completion
Notes
- Instructions must be very clear with code snippets and file paths
- If implementation proceeds, keep one primary implementation authority unless the write scopes are clearly disjoint
- The final review must check both task completion and whether the implementation still satisfies the user's original intent
- I will not implement anything until the user approves
User Query: $ARGUMENTS