Verified:GitHub

history-hygiene

Record confirmed final outcomes to history.md and update reversed decisions.

Updated Apr 10, 2026

Search Tags:#documentation #history #knowledge-management #outcomes #team-collaboration #decision-tracking #decision-log

Ready to run

npx skills add https://github.com/chdaly/eshop --skill history-hygiene-chdaly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/chdaly/eshop --skill history-hygiene-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files (.md files tracking decisions, spawns, outcomes) are read cold by future agents. Stale or incorrect entries poison decision-making downstream. The Kobayashi incident proved this: history said "Brady decided v0.6.0" when Brady had reversed that to v0.8.17. Future spawns read the wrong truth and repeated the mistake.

Core Features & Use Cases

Record the final outcome, not intermediate requests or reversals. Update entries if a decision changes, maintaining a single source of truth for future agents.
Wait for confirmation before writing to history to avoid premature entries.
One read = one truth. The history should be the authoritative record of what actually happened, not what was requested or proposed.

Quick Start

Log the final decision outcome to history.md after confirmation, and update it immediately if the decision reverses.

Frequently Asked Questions about history-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent stale decision log entries from misleading future agents?▼

Update decision tracking history immediately when a decision reverses to maintain a single source of truth. This prevents future agents from acting on stale or conflicting records that no longer reflect the actual final outcome.

What is the best way to maintain history.md files for team collaboration workflows?▼

The best way to maintain history.md files is to record only final outcomes and enforce confirmation before logging entries. This creates an authoritative record of actual events rather than proposals or partial states for team collaboration workflows.

Why does my decision tracking history show outdated information after a reversal?▼

Decision tracking history shows outdated information when intermediate requests are logged instead of final outcomes. Without immediate updates to history.md upon reversals, future agents read stale entries and act on incorrect truth.

When should I write outcomes to history.md in an archival workflow?▼

Write outcomes to history.md in archival workflows only after receiving explicit confirmation of the final decision. Logging prematurely captures intermediate states that may reverse and poison downstream decision-making for future agents reading the file cold.

Can I update a history.md entry if a team decision changes after it was originally logged?▼

Yes, you can and should update a history.md entry immediately if a team decision reverses. The history file must reflect the current single source of truth, so updating reversed decisions prevents future agents from acting on stale records.