history-hygiene

To log only final outcomes to a history file, you describe the conclusive result and the skill appends it to history.md after explicit confirmation. This prevents intermediate requests from polluting the audit trail.

The best way to track decision reversals in an audit trail is to use a logging discipline that updates history.md when a decision is reversed. This preserves traceability by recording the corrected outcome over the initial request.

Decision-tracking maintains a single source of truth by ensuring future agents reference the conclusive result in history.md instead of intermediate requests. It records only final outcomes and supports automatic updates when outcomes change.

You do not need to manually edit history.md when a project decision is corrected. The skill supports automatic updates to the audit trail when outcomes change, ensuring the file reflects the final result.

Your history file makes future work brittle because the audit trail is polluted by intermediate requests or reversed decisions. Recording only final outcomes in history.md ensures a reliable source of truth for future reference.

You can review a final outcome before it gets logged to the audit trail. The skill requires explicit confirmation before appending any final outcomes to history.md, preventing unwanted or premature entries.