mcpField
D
decision-drift-guard

decision-drift-guard

github.com/darknesskillerAgent workflows092 installsUpdated 2w ago
Repository

About decision-drift-guard

decision-drift-guard is an agent skill for recording and handling changes to accepted user decisions. It classifies new instructions and pauses for confirmation when they supersede or conflict with an existing decision.

Key features

  1. 01Maintain a session-specific decision ledger
  2. 02Classify instructions against active decisions
  3. 03Request confirmation for conflicts or replacements
  4. 04Recompute downstream plans after confirmation

Use cases

  1. 01Track accepted decisions across a session
  2. 02Handle new instructions that conflict with a chosen approach
  3. 03Confirm decision changes before consequential work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/darknesskiller/skills --skill decision-drift-guard

After installing, type/decision-drift-guardin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Decision Drift Guard

A supersession is a new accepted user decision replacing an earlier one. Make it explicit before consequential work.

Steps

  1. Load the ledger. Path: .agents/decision-ledger/sessions/<session-id>.md relative to worktree root. Use host session ID or derive from first request. Each session reads/writes only its own file. Filesystem fails: keep ledger in context, say persistence unavailable.

  2. Track decisions. One line per active decision: D-<n> | scope | chosen approach | acceptance. Suggestions stay proposed until user accepts.

  3. Classify new statement against active decisions in same scope:

Statement means...ClassAction
Same meaningsamecontinue
Adds detail or fixes mistakerefinementupdate record
Separate scopebranchcreate record
"Use this instead"supersessionrun Gate 1
Cannot both holdconflictrun Gate 1
Cannot tellunclearask one question

Watch for: "actually", "instead", "forget that", "on second thought". Compare meaning, not phrase overlap.

  1. Gate 1 (supersession or conflict only): Show old decision, new instruction, impact. Ask: replace, branch, or refine. Wait for choice.

  2. Gate 2 (after replacement confirmed): Touches architecture, public behavior, data shape, security, cost, or irreversible actions: run /grilling and wait. Otherwise: which old assumption dies, what changes, what must stay.

  3. Commit supersession. Mark old record superseded. Link new with supersedes: D-<n>. Recompute plan, tests, tool actions. Label stale recommendations.

Completion: one active record per replaced scope, every downstream action uses it.

First pass format

  • Ledger: loaded or unavailable.
  • Classification: supersession or conflict.
  • Old decision: <old>. New instruction: <new>. Impact: <changes>.
  • Paused. Choose: replace, branch, or refine.

Comments

Markdown supported