skills.rest
elbruno
elbrunoCOMMUNITY
Explore all skills by this author →
Website𝕏@elbrunoGitHub

history-hygiene

Record confirmed final outcomes to history files instead of intermediate or reversed decisions.

2|Updated Jul 24, 2026
Search Tags:#documentation#knowledge management#decision tracking#team collaboration#multi-agent workflows#history files
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill history-hygiene-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/history-hygiene
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill history-hygiene-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? History files tracking decisions and outcomes are read cold by future agents, so stale or premature entries poison downstream decision-making. This Skill prevents recording intermediate requests or reversed decisions as if they were final truth. ## Core Features & Use Cases - Final-outcome recording: Write only confirmed results to history.md, never intermediate or "for now" states. - Reversal handling: Update entries immediately when a decision is reversed so no stale data remains. - Single-source-of-truth discipline: Ensure one read gives one truth, with no cross-referencing required by future readers. - Use Case: A migration target is discussed as v0.6.0 but later corrected to v0.8.17; the history entry records "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)" so future agents act on the right version. ## Quick Start Before writing any decision or outcome to a history file, confirm the final state and record only the confirmed outcome with a note of any reversal.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I keep decision history files accurate for future readers?▼

Record only confirmed final outcomes, not initial requests or intermediate states. Wait for explicit confirmation before writing, and if a decision is later reversed, update the entry immediately so no stale data remains.

What should I write to a history file when a decision gets reversed?▼

Write the final outcome with a brief note of the reversal, for example: "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)". Never leave the original reversed decision standing as the recorded truth.

Why is logging intermediate states to history files harmful?▼

History files are read cold by future agents who treat them as the source of truth. Intermediate or unconfirmed entries cause readers to act on wrong information, as happened when a reversed v0.6.0 decision was repeated by later spawns.

When should I not write to a history file?▼

Do not write before an outcome is confirmed, when a decision is still under discussion, or when you would be recording what was requested rather than what actually happened. History is not a draft; it is the source of truth.

Should history entries require cross-referencing other files?▼

No. Each entry should be self-contained so one read gives one truth. Future readers will not cross-reference or verify, so include enough context, such as dates and who confirmed the decision, directly in the entry.

Related Skills

Explore More Product & Management Skills→
semicolon-devteamsemicolon-devteam

create-decision-log

Compile meeting, Slack, and PR decisions into a GitHub Discussion.

Official
Advanced
kay6198835kay6198835

retrospective

Generate structured sprint retrospectives from project data and git history.

Community
Advanced
mark-brannanmark-brannan

reconcile

Verifies board cards and memos against GitHub state and corrects stale records.

Community
Intermediate
anthropicsanthropics
9.1k

uninstall

Uninstall hub-installed community skills while protecting first-party plugins and logging actions.

Official
Intermediate