devlyn-cli 0.5.4 → 0.5.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -471,7 +471,7 @@ After receiving all teammate findings:
|
|
|
471
471
|
1. Read all findings carefully
|
|
472
472
|
2. If teammates disagree on root cause → re-examine the contested evidence yourself by reading the specific files and lines they reference
|
|
473
473
|
3. Compile a unified root cause analysis
|
|
474
|
-
4. If the fix is complex (multiple files, architectural change) → enter plan mode and present to user for approval
|
|
474
|
+
4. If the fix is complex (multiple files, architectural change) → call the `EnterPlanMode` tool to enter plan mode and present the implementation plan to the user for approval before writing any code
|
|
475
475
|
5. If the fix is simple and all teammates agree → proceed directly
|
|
476
476
|
|
|
477
477
|
Present the synthesis to the user before implementing.
|
|
@@ -492,7 +492,7 @@ Workaround indicators (if you catch yourself doing any of these, STOP):
|
|
|
492
492
|
|
|
493
493
|
If the true fix requires significant refactoring:
|
|
494
494
|
1. Document why in the root cause analysis
|
|
495
|
-
2.
|
|
495
|
+
2. Call the `EnterPlanMode` tool to present the scope to the user and get approval before proceeding
|
|
496
496
|
3. Get approval before proceeding
|
|
497
497
|
4. Never ship a workaround "for now"
|
|
498
498
|
</no_workarounds>
|