skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

history-hygiene

Record only final confirmed decisions to history.md.

Updated Mar 27, 2026
Search Tags:#documentation#audit#history#truth#team-collaboration#decision-tracking#history-trail
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill history-hygiene-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill history-hygiene-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files tracking decisions can become stale when intermediate requests or reversals are logged. This Skill ensures only final outcomes are recorded to history.md, preventing outdated entries from misguiding future agents.

Core Features & Use Cases

  • Final-outcome logging: write only the conclusive decision to the history trail.
  • Update-on-reversal: modify history entries immediately when decisions change.
  • One-truth principle: future readers should rely on a single, authoritative record.

Quick Start

Log the final outcome to history.md after confirmation, and do not record interim states.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I record only final outcomes to a decision history trail without logging intermediate requests?▼

To record final outcomes to a decision history trail, log only the conclusive decision to history.md after confirmation, avoiding any intermediate states or reversed decisions to maintain an authoritative record.

Why does my team collaboration history file contain stale entries from reversed decisions?▼

Team collaboration history files become stale when intermediate requests or reversed decisions are logged. Update history.md entries immediately upon decision reversals to prevent outdated records from misguiding future agents.

What is the one-truth principle for decision-tracking in documentation?▼

The one-truth principle for decision-tracking ensures future readers rely on a single, authoritative history.md record. It requires deterministic logging where updates are written only after final confirmation.

How do I update history.md when a multi-step decision process reverses a previous outcome?▼

To update history.md when a multi-step decision process reverses, modify the existing history entry immediately upon the reversal. Do not append new interim logs; rewrite the record to reflect the final confirmed state.

When should I not use an audit trail for intermediate requests in team collaboration?▼

You should not use an audit trail for intermediate requests in team collaboration when building a deterministic history.md. Logging interim states creates stale entries; only final, confirmed outcomes belong in the history trail.

Does this decision-tracking approach work for any multi-step decision process across teams?▼

Yes, this decision-tracking approach applies to any multi-step decision process across teams. It enforces immediate updates on reversals and deterministic logging to ensure history.md contains only final, confirmed outcomes.

Related Skills

Explore More Content & Communication Skills→
sachinnair90sachinnair90

history-hygiene

Record only final confirmed outcomes in markdown history files.

Community
Basic
robpitcherrobpitcher

history-hygiene

Record confirmed final outcomes to history.md after explicit confirmation.

Community
Intermediate
haidonglethqbhaidonglethqb

ck:project-management

Track plan progress and generate status updates across multiple plans.

Community
Advanced
acmelemeacmeleme

history-hygiene

Record final decision outcomes to history.md after confirmation.

Official
Intermediate