Skip to content

Commit c6ad6b8

Browse files
committed
Include technical recommendation and axis separation in /apply-findings Step 3
1 parent 876236d commit c6ad6b8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

skills/apply-findings/SKILL.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If a finding references code that has changed since it was generated (e.g., by a
2626

2727
## Step 3: Handle Escalated Findings
2828

29-
For findings with Escalate verdict, use `AskUserQuestion` to present the trade-offs and let the user decide:
29+
For findings with Escalate verdict, use `AskUserQuestion` to present the trade-offs and let the user decide. Include your technical recommendation alongside the options. When options differ on both scope/intent adherence (what the task was scoped to do) and technical merit (what's engineering-wise better), state both axes explicitly — don't silently fold scope concerns into the technical recommendation.
3030

3131
- **Apply** — make the change
3232
- **Skip** — leave as-is

0 commit comments

Comments
 (0)