From d00de60356d6bc68b324020bc008308c2bbe6774 Mon Sep 17 00:00:00 2001 From: kmaclip Date: Fri, 27 Mar 2026 10:56:09 -0400 Subject: [PATCH] fix: remove preemptive context warnings in plan-eng-review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The priority hierarchy instruction tells the model to watch for low context, which causes premature compression warnings on 1M context window models (e.g., Claude Opus 4.6). At 27% usage on a 1M window, ~730K tokens remain — nowhere near a real constraint. The fix: - Removes "running low on context" trigger (model can't accurately gauge this and becomes overly cautious) - Keeps the user-initiated "asks you to compress" trigger - Adds system compaction trigger (Claude Code handles this natively) - Explicitly tells the model not to preemptively warn about limits This was calibrated for 200K windows. On 1M models, the old thresholds caused unnecessary anxiety and premature summarization. Closes #510 --- plan-eng-review/SKILL.md | 2 +- plan-eng-review/SKILL.md.tmpl | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md index 9720f1b49..dc161fa73 100644 --- a/plan-eng-review/SKILL.md +++ b/plan-eng-review/SKILL.md @@ -330,7 +330,7 @@ plan's living status. Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. ## Priority hierarchy -If you are running low on context or the user asks you to compress: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. +If the user asks you to compress or the system triggers context compaction: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. Do not preemptively warn about context limits — the system handles compaction automatically. ## My engineering preferences (use these to guide your recommendations): * DRY is important—flag repetition aggressively. diff --git a/plan-eng-review/SKILL.md.tmpl b/plan-eng-review/SKILL.md.tmpl index b1f05a03d..2c5043245 100644 --- a/plan-eng-review/SKILL.md.tmpl +++ b/plan-eng-review/SKILL.md.tmpl @@ -27,7 +27,7 @@ allowed-tools: Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. ## Priority hierarchy -If you are running low on context or the user asks you to compress: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. +If the user asks you to compress or the system triggers context compaction: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. Do not preemptively warn about context limits -- the system handles compaction automatically. ## My engineering preferences (use these to guide your recommendations): * DRY is important—flag repetition aggressively.