history-hygiene

Records final confirmed outcomes to history.md and updates entries on decision reversals.

3|5|Updated Mar 19, 2026

Search Tags:#documentation #auditing #history #team-collaboration #decision-tracking #log-management #final-outcome

Ready to run

npx skills add https://github.com/ronniegeraghty/hyoka --skill history-hygiene-ronniegeraghty

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files track decisions and outcomes, but logging intermediate steps or reversals leads to confusion and misinformation. This Skill ensures only final, confirmed results are written to history.md, preserving a reliable record for future agents.

Core Features & Use Cases

Record final outcomes to history.md to maintain a single source of truth for decision trails.
Update history entries immediately when decisions are reversed to reflect the true outcome.
Prevent logging intermediate states or speculative notes that could mislead future spawns or audits.
Use Case: When a decision changes from v1 to v2, the final outcome "v2" is recorded, and prior intermediate states are not retained.

Quick Start

Write only the final confirmed outcome to history.md in your decision logs.

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 decisions from cluttering my history logs?▼

Prevent stale decisions in history logs by recording only final, confirmed outcomes to history.md. This ensures future agents rely on a single source of truth without being misled by intermediate states or speculative notes.

What is the best way to track decision reversals in a team collaboration log?▼

Track decision reversals in a team collaboration log by updating the existing history.md entry immediately when a decision changes. This reflects the true final outcome and overwrites prior intermediate states to maintain an accurate decision trail.

Does this decision-tracking method work for workflows with frequent updates?▼

Yes, decision-tracking works for workflows with frequent updates by enforcing immediate entry updates on reversals. When a decision changes from v1 to v2, only the final outcome v2 is recorded, excluding all intermediate states.

When should I not log intermediate states to a history file?▼

You should not log intermediate states to a history file when future agents rely on a single source of truth. Logging speculative notes or unconfirmed steps leads to confusion and misinformation during team collaboration and auditing.

How do I maintain a single source of truth for decision trails?▼

Maintain a single source of truth for decision trails by writing only final confirmed outcomes to history.md. This log management practice prevents misleading information and ensures future spawns access reliable, confirmed results.