history-hygiene

To prevent stale decision-tracking entries, this Skill enforces final-state logging by waiting for explicit confirmation before writing to history.md and immediately updating any prior entry when a decision is reversed.

Team-collaboration history files often incorrectly log proposed or intermediate requests instead of the final outcome. This Skill solves the problem by enforcing final-state logging, ensuring future agents consulting the single source of truth read what actually happened, not what was initially requested.

Maintaining a single source of truth for decision-tracking requires enforcing final-state logging in history.md. This Skill records only confirmed outcomes and immediately updates entries when decisions reverse, ensuring future agents read accurate history.

You can update a history.md entry automatically when a decision is reversed. This Skill immediately modifies prior entries to reflect the reversal, ensuring the single source of truth remains accurate for future agents.

You should avoid writing intermediate requests to decision-tracking history files until the final outcome is confirmed. This Skill waits for explicit confirmation before writing, preventing premature entries from corrupting downstream agent decisions.