history-hygiene

Log final decision outcomes to history.md and update entries on reversals.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill history-hygiene-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/quaid-app/quaid --skill history-hygiene-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files tracking decisions, spawns, and outcomes can become stale or incorrect, causing future agents to repeat the same mistakes or rely on outdated context.

Core Features & Use Cases

  • Record the final outcome only, not intermediate requests or draft states.
  • Update entries immediately when a decision is reversed to keep history accurate.
  • Maintain a single source of truth for postmortems and retrospectives to guide future actions.

Quick Start

After a decision is finalized, update history.md with the final outcome and remove or override any earlier intermediate records.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I maintain a decision log that doesn't get cluttered with intermediate states?

To maintain a clean decision log, record only the final outcome to history.md instead of intermediate requests or draft states. This prevents stale entries and ensures future reference relies on authoritative, finalized decisions rather than outdated context.

What is the best way to track reversed decisions in an incident postmortem?

Tracking reversed decisions in an incident postmortem requires immediately updating the existing history.md entry when a reversal occurs. This enforces accurate team retrospectives by overriding earlier records and maintaining a single source of truth.

Can I use history.md for team retrospectives where outcomes frequently change?

Yes, history.md suits team retrospectives where outcomes change by enforcing immediate updates to reversed decisions. It prevents logging intermediate states, ensuring the retrospective reflects only the final, authoritative outcomes for reliable future reference.

Why does my version control history contain stale or incorrect decision records?

Version control history becomes stale when intermediate requests or draft states are logged instead of final outcomes. Logging only finalized decisions to history.md and updating entries immediately upon reversals prevents future agents from relying on outdated context.

When should I not use a single history file for team collaboration documentation?

You should not use a single history file for tracking intermediate work states or draft proposals. history.md is designed exclusively for final outcomes and decision logs, meaning it lacks the structure needed for ongoing, unfinalized team collaboration documentation.