| 对比新文件 |
| | |
|---|
| | | --- |
|---|
| | | 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鈥檚 Razor鈥攑rioritize 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. |
|---|
