| name | correction-tracking |
| description | This skill should be used when the user redirects, corrects, or refines agent output — "no, actually", "that's not right", "you missed something". Captures correction moments to improve Forge workflows over time. Always active during feature work; log corrections as they occur. |
Correction Tracking Pattern
All Forge agents should track "correction moments" — instances
where the user redirects, corrects, or refines the agent's
output. These are valuable signals for workflow improvement.
Note Format with Status Tracking
Each note includes a status marker for incremental processing
by /forge:improve.
## YYYY-MM-DD: {Phase}
### Note {N}: {Brief Title}
<!-- STATUS: UNPROCESSED -->
**Context:** ...
**What happened:** ...
**Recommendation:** ...
---
Status values:
UNPROCESSED — New note, not yet reviewed by auditPROCESSED: {date} | Applied: {file} | PR: #{pr} —
Change was madePROCESSED: {date} | Skipped: {reason} — Decided not to
actPROCESSED: {date} | Deferred: #{issue} — Created ticket
for later
Notes without any status marker are treated as UNPROCESSED
(for backwards compatibility with existing notes).
What is a Correction?
A correction occurs when the user:
- Says "no, actually..." or "that's not right..."
- Provides significantly different input than what was
suggested
- Asks the agent to redo or revise work
- Points out something the agent missed or assumed
incorrectly
- Manually edits agent-generated content substantially
