skills.rest
nicolehaugen
nicolehaugenCOMMUNITY
Explore all skills by this author →
GitHub

history-hygiene

Record final project decisions in history.md after confirmation.

Updated Apr 8, 2026
Search Tags:#decision making#team collaboration#document integrity#history maintenance#history recording
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill history-hygiene-nicolehaugen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/history-hygiene
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill history-hygiene-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain the integrity of historical records by ensuring that only final outcomes are recorded, reducing the risk of misinformation and decision-making errors.

Core Features & Use Cases

  • Final Outcome Recording: Ensures that only the final decisions and outcomes are documented in history files.
  • Confirmation-Based Logging: Prompts for confirmation before writing to history, avoiding recording intermediate states.
  • Decision Reversal Handling: Updates history entries immediately upon reversal of decisions, preventing stale data.
  • Single Source of Truth: Provides a clear, unambiguous history for future reference, eliminating the need for cross-referencing.

Quick Start

Use the history-hygiene skill to record the final outcome of a project decision in the history.md file.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I ensure only final outcomes are recorded in history files?▼

History recording requires confirmation before logging to ensure only final outcomes are written to history files, which prevents documenting intermediate states and reduces the risk of misinformation in team collaboration.

What is the best way to handle decision reversal in history maintenance?▼

History maintenance handles decision reversal by immediately updating history entries upon reversal, preventing stale data and maintaining a single source of truth for future reference.

Why does recording intermediate states cause decision-making errors in team collaboration?▼

Recording intermediate states causes decision-making errors by introducing misinformation and stale data into history files, which necessitates cross-referencing and obscures the single source of truth for the team.

Can I use history hygiene for team collaboration documentation?▼

Yes, history hygiene applies directly to team collaboration and documentation processes, providing an unambiguous history that eliminates the need for cross-referencing and supports informed decisions.

Related Skills

chdalychdaly

history-hygiene

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

Community
Intermediate
rubenslivrubensliv
15

flowio

Parse FCS 2.0 to 3.1 files to extract event data and metadata.

Community
Advanced
webmaxruwebmaxru
49

history-hygiene

Record only final outcomes to history.md with time-stamped entries.

Community
Intermediate
ronniegeraghtyronniegeraghty
3

history-hygiene

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

Community
Intermediate