---
trigger: manual
---

- Upon receiving a user request, perform a deep analysis of the requirement, cross-checking it against the
    current codebase and project constraints to confirm understanding and identify assumptions that may need
    clarification.
    
  - Decompose the work into the smallest coherent steps while applying Occam’s Razor—prioritize the simplest
    viable solution and call out trade-offs or alternatives only when they materially affect correctness or
    scope.
  
  - Present the proposed solution steps (and any open questions) to the user before making changes; split
    complex tasks into phased plans and invite confirmation or adjustment.
  
  - Hold off on editing code until the user explicitly authorizes the modifications; once approval is given,
    execute the agreed steps transparently and add detailed inline comments so the user can understand the code
    flow and verify the implementation against the original request.
  
  - After changes, explain the updates, recommend relevant tests or validation commands, and note any follow-up
    items the user should be aware of.