operation-tracker

---

name: operation-tracker description: Maintain awareness of operation counts across the conversation to prevent cumulative context exhaustion. Use when you notice multiple operations accumulating or when working on iterative tasks across turns. allowed-tools:

• Task
• AskUserQuestion

---

The per-turn threshold is a trap—it's the CONVERSATION-LEVEL accumulation that kills sessions. This skill helps Claude track operations and recognize when to delegate.

<quick_start> <mental_tracking> Before each operation, mentally note:

1. Reads since last Task: How many files have I read directly since my last Task delegation?
2. Edits since last Task: How many edits have I made since my last Task delegation?
3. Same-file turns: Am I iterating on the same file across multiple turns?
4. Continue loops: Is the user saying "continue" or similar repeatedly?

If any count exceeds threshold → delegate remaining work. </mental_tracking>

<iteration_patterns> User keeps saying "continue", "keep going", "more", etc. Each turn adds context without triggering delegation consideration.

Then delegate via Task(general-purpose).

<tracking_method> Mental checklist at start of each turn:

• "Since my last Task delegation, I've done [N] edits"
• If N ≥ 3: "I should delegate remaining edits" </tracking_method>

<regression_detection> Notice when you start a task with proper delegation but gradually revert to direct execution.

If yes to all three: you're regressing.

Task(general-purpose): "Complete the remaining [work description]" </regression_detection>

<context_checkpoints> After any exploration phase (Grep, Glob, multiple Reads):

• Check: Did I load significant content into context?
• If yes: Delegate action phase to preserve context

<communication_templates> "I've done [N] [operations] since my last delegation. To preserve context for the rest of our session, I'll delegate the remaining [work type]."

<anti_patterns> Wrong: Checking thresholds only within current turn Right: Track cumulative operations since last Task delegation

<success_criteria> The tracking is working when:

• You can mentally state operation counts at any point
• Delegation happens BEFORE thresholds are exceeded
• Iteration loops are recognized and addressed
• Regression from delegation is caught and corrected
• Long sessions maintain consistent context usage
• User is informed when delegation decisions are made </success_criteria>

delegate-first answers: "Should this be delegated?" operation-tracker answers: "Have I accumulated too much?"

Use together: delegate-first for new operations, operation-tracker for ongoing awareness. </with_delegate_first>