skills.rest
webmaxru
webmaxruCOMMUNITY
Explore all skills by this author →
Website𝕏@webmaxruGitHub

history-hygiene

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

49|6|Updated Aug 24, 2021
Search Tags:#documentation#collaboration#logging#audit#history#decision-tracking#team-workflow
One-click install
npx skills add https://github.com/webmaxru/bpm-counter --skill history-hygiene-webmaxru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/webmaxru/bpm-counter/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/webmaxru/bpm-counter --skill history-hygiene-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files tracking decisions can become noisy or inconsistent when intermediate requests or reversals are logged. This Skill ensures only final outcomes are recorded to history.md, preserving a reliable record for future readers.

Core Features & Use Cases

  • Final-outcome logging: Writes only the confirmed end state to history.md, avoiding noise from tentative steps.
  • Change reconciliation: Automatically updates history when a decision is reversed to reflect the latest outcome.
  • Audit-friendly history: Produces clear, time-stamped entries that serve as a single source of truth for teams.

Quick Start

Log the final decision to history.md after the decision is confirmed.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
How do I log only final decisions to a history file without recording intermediate steps?▼

Decision log reconciliation automatically updates history.md when a decision is reversed to reflect the latest outcome. This enforces that history entries reflect final states, providing auditable traceability for project retrospectives.

Why does my team decision log contain noisy or inconsistent intermediate requests?▼

Writing only final outcomes to history.md prevents stale or reversed decisions from polluting future spawns. It automatically updates history on reversals, providing auditable traceability and a reliable record for team decision logs.

What is the best way to maintain an audit-friendly history for project retrospectives?▼

The best way to maintain an audit-friendly history is to write only confirmed final outcomes to history.md. This produces clear, time-stamped entries that serve as a single source of truth, avoiding noise from tentative steps in team workflows.

How do I update a decision log when a previous team decision is reversed?▼

To update a decision log after a reversal, apply change reconciliation to immediately update history.md with the latest outcome. This ensures the history file reflects the final state rather than the stale initial decision.

Does writing final outcomes to history.md work for team workflow documentation?▼

Yes, writing final outcomes to history.md works for team workflow documentation by enforcing that history entries reflect final states. It supports immediate updates on reversals, making it ideal for team decision logs and project retrospectives.

Related Skills

Explore More Content & Communication Skills→
WayneWalterBerryWayneWalterBerry

history-hygiene

Record final, confirmed decisions to history.md after they are made.

Community
Intermediate
skwuwuskwuwu

gvm_audit

Verify GVM audit log integrity and export compliance reports.

Community
Intermediate
chdalychdaly

history-hygiene

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

Community
Intermediate
olivomarcoolivomarco
66

history-hygiene

Record confirmed final outcomes to history.md and update reversals immediately.

Community
Intermediate