skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

history-hygiene

Record final decision outcomes to history.md and update entries on reversals.

1|Updated Apr 18, 2026
Search Tags:#documentation#history#outcomes#team-collaboration#audit-trail#decision-log
One-click install
npx skills add https://github.com/DeDuva/squad --skill history-hygiene-deduva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-cli/templates/skills/history-hygiene
Command: npx skills add https://github.com/DeDuva/squad --skill history-hygiene-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files track decisions, spawns, and outcomes, but often capture intermediate states or reversals. This Skill ensures history.md reflects final outcomes, providing a reliable single source of truth for future agents.

Core Features & Use Cases

  • Record the final outcome of decisions to history.md, ensuring a clean, auditable archive.
  • Update history entries immediately when a decision is reversed, preventing stale records.
  • Maintain a succinct, goal-oriented history for team alignment and project audits.

Quick Start

Log only final outcomes to history.md and update entries promptly when reversals occur.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema
What should be recorded in a decision log to maintain a reliable audit trail?▼

Record only final outcomes to history.md, excluding intermediate requests or draft states, to maintain a clean and auditable decision log for future agents.

How do I update team collaboration history when a project decision is reversed?▼

Update history.md entries immediately when a decision is reversed to prevent stale records and ensure the final direction accurately reflects the current truth.

Why does my documentation include unconfirmed draft states in the history file?▼

Documentation includes draft states when intermediate requests are logged; history.md should avoid logging unconfirmed states and only store final outcomes for team alignment.

Can I use history.md to track intermediate requests for project decisions?▼

No, history.md is designed to document final outcomes only. It should not track intermediate requests, ensuring a succinct, goal-oriented history for project audits.

What is the best way to maintain a single source of truth for team collaboration outcomes?▼

Record final outcomes to history.md and update entries immediately upon reversals, avoiding unconfirmed draft states, to maintain a reliable single source of truth for team collaboration.

Related Skills

Explore More Content & Communication Skills→
nicolehaugennicolehaugen

history-hygiene

Record final project decisions in history.md after confirmation.

Community
Intermediate
forbotsakeforbotsake
5

learn

Aggregate and index project learnings across sessions in JSONL stores.

Official
Advanced
Golnaz89Golnaz89

history-hygiene

Record final outcomes to history.md after explicit confirmation.

Community
Intermediate
olivomarcoolivomarco
66

history-hygiene

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

Community
Intermediate