Correction Memory

The Problem

When you correct an agent, that correction evaporates after the session. Next time you spawn the same agent type, it makes the same mistake. There's no memory of what you've already taught it.

What This Skill Installs

• - lib/correction-tracker.js — logs corrections per agent type to INLINECODE1
• Hook into agent-context-loader.js — correction preamble prepended to spawns automatically (if intent-engineering is also installed)

Installation

Step 1 — Install correction-tracker

CODEBLOCK0

Verify it runs:

CODEBLOCK1

Step 2 — Wire agent-context-loader (if using intent-engineering)

If lib/agent-context-loader.js is installed (from intent-engineering skill), correction injection is automatic — no wiring needed. The loader checks for correction-tracker.js at startup and loads it if present.

If you are NOT using intent-engineering, add this to your spawn logic manually:

CODEBLOCK2

Logging Corrections

Programmatic

CODEBLOCK3

Via main agent (natural language)

Just tell the main agent:

"Note that [AgentType]: [what it did wrong] — [correct behavior]"

The main agent will log it programmatically.

How Corrections Are Replayed

On every subagent spawn, agent-context-loader detects the agent type from the task description and prepends:

CODEBLOCK4

Only corrections from the last 30 days are injected. Older corrections expire automatically — stale rules don't accumulate.

Viewing Corrections

CODEBLOCK5

Agent Type Detection

The loader auto-detects agent type from the task description. Default rules:

To add custom agent types, edit detectAgentType() in agent-context-loader.js.

References

• - references/correction-tracker-template.js — Full implementation of correction-tracker.js