skills.rest
sudhakrms
sudhakrmsCOMMUNITY
Explore all skills by this author →
GitHub

history-hygiene

Record final decision outcomes to history.md after confirmation.

1|Updated Apr 17, 2026
Search Tags:#logging#history#team-collaboration#audit-trail#decision-record#final-outcome
One-click install
npx skills add https://github.com/sudhakrms/CalendarControl --skill history-hygiene-sudhakrms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill history-hygiene-sudhakrms

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 to ensure the history reflects actual decisions, not intermediate steps.
  • Wait for confirmation before logging to prevent premature entries and maintain truth.
  • Immediately update reversals so history always reflects the latest, confirmed direction.
  • One read = one truth to avoid cross-referencing multiple files for context.

Quick Start

Record the final outcome to history.md once a decision is finalized.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I record final decisions to a history.md audit trail?▼

Record final outcomes to history.md to ensure a single source of truth. Apply to team decision workflows, project changes, and reversal events where final direction must be captured.

When should I update a decision record after a reversal?▼

Immediately update reversals in the decision record so history always reflects the latest confirmed direction. Wait for confirmation before logging to prevent premature entries and maintain truth.

Why does logging intermediate steps to history files cause problems?▼

Logging intermediate steps poisons downstream decision-making. History files are read cold by future agents, and stale or incorrect entries cause them to read the wrong truth and repeat mistakes.

What is the best way to maintain a single source of truth for team collaboration history?▼

Maintain a single source of truth by logging only final states to history.md after confirmation. This ensures one read equals one truth and avoids cross-referencing multiple files for context.

Can I log project changes to history.md before a decision is finalized?▼

No, you must wait for confirmation before logging to prevent premature entries. Recording final outcomes ensures the history reflects actual decisions, not intermediate steps.

Does history.md logging work for tracking team decision workflows and reversal events?▼

Yes, history.md logging applies directly to team decision workflows, project changes, and reversal events. It ensures final direction is captured and immediately updated when decisions reverse.

Related Skills

Explore More Content & Communication Skills→
quaid-appquaid-app
3

history-hygiene

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

Official
Intermediate
chdalychdaly

history-hygiene

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

Community
Intermediate
gonzalezpazmonicagonzalezpazmonica
47

governance-enterprise

Orchestrate enterprise governance workflows for audit trails, compliance, and certifications.

Community
Advanced
acmelemeacmeleme

history-hygiene

Record final decision outcomes to history.md after confirmation.

Official
Intermediate