history-hygiene

Log final decision outcomes to history.md after explicit confirmation.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill history-hygiene-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/sytone/botnexus --skill history-hygiene-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files that track decisions, spawns, and outcomes are consumed by future agents. Logging intermediate states or reversed decisions can mislead teams and cause repeated mistakes. This Skill ensures only final outcomes are recorded, preserving a single source of truth.

Core Features & Use Cases

  • Record final-outcome logging only
  • Update history when decisions reverse, keeping history accurate
  • Supports team collaborations by maintaining a single truth for future agents

Quick Start

Log the final decision outcome to history.md after confirmation to maintain a reliable record.

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 outcomes to history.md and prevent intermediate decisions from being recorded?

To maintain a single truth in history files, you must record only final decisions while updating or removing entries when previous decisions reverse. This prevents future agents from acting on outdated intermediate states and avoids repeated mistakes.

How do I maintain a single source of truth in team collaboration history files when decisions evolve?

Maintaining a single source of truth in team collaboration history files requires updating entries when decisions reverse. This ensures future agents always rely on an authoritative history rather than conflicting intermediate logs.

What is final-state logging for decision-tracking and when do I need it in multi-agent workflows?

Final-state logging for decision-tracking records only the ultimate outcomes in history.md, omitting intermediate requests. You need it in multi-agent workflows where future agents consume history files and rely on accurate, authoritative records.

Can I use history logging for multi-agent workflows without manually filtering reversed decisions?

Yes, you can log history for multi-agent workflows without manual filtering by using a skill that automatically enforces final-state logging. It updates history.md entries upon decision reversals to maintain accuracy without manual intervention.

Why does logging intermediate states in documentation history mislead future agents?

Logging intermediate states in documentation history misleads future agents because they consume these files expecting an authoritative record. Intermediate requests or reversed decisions create conflicting truths, causing agents to repeat mistakes or act on invalid data.