decision-lock-hygiene

Archive superseded decisions and verify consistency after a decision lock.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill decision-lock-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-lock-hygiene
Source: https://github.com/Scripsteam/scrips-stack/tree/main/decision-lock-hygiene
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill decision-lock-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mandatory post-lock cleanup ensures no superseded guidance lingers by archiving outdated decisions and artifacts, then verifies there are no conflicting answers in any source.

Core Features & Use Cases

  • Retire superseded decisions and related artifacts across sources to prevent drift.
  • Verify consistency by scanning for contradictions after a lock and producing an auditable trail.
  • Provide governance-friendly remediation with clear deprecation notes and archivals.

Quick Start

Run the hygiene pass immediately after a decision lock to archive superseded items and verify consistency across sources.

Frequently Asked Questions about decision-lock-hygiene

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

FAQPage Schema
How do I archive outdated design documents after a decision is locked?

Archive outdated design documents by running a post-lock hygiene pass that retires superseded artifacts and adds deprecation notes. This ensures outdated guidance does not influence future work and creates an auditable trail of changes.

What is the best way to prevent stale knowledge sources from creating conflict after a decision lock?

Preventing stale knowledge sources from creating conflict requires a post-lock verification scan. This process identifies contradictions across sources after a decision lock, archives superseded items, and establishes a canonical source for current answers.

How do I verify consistency across knowledge management sources once requirements change?

Verifying consistency across knowledge management sources involves scanning for contradictions immediately after a decision lock. The process retires superseded requirements, archives outdated artifacts, and produces an auditable trail confirming a consistent post-lock state.

When do I need to run a post-decision hygiene pass for archiving and verification?

You need to run a post-decision hygiene pass immediately after a decision lock. This ensures that superseded guidance is archived and that no conflicting answers remain in any source, maintaining a consistent post-lock state.

Can I use decision-lock hygiene to handle conflict resolution across multiple knowledge sources?

Decision-lock hygiene handles conflict resolution by scanning for contradictions across multiple sources after a lock. It requires a canonical source for current answers and provides governance-friendly remediation with clear archivals and deprecation notes.

Does post-decision archiving work without a canonical source for current answers?

Post-decision archiving does not work effectively without a canonical source. The hygiene process requires a canonical source for current answers to resolve conflicts and ensure that archiving outdated decisions results in a consistent post-lock state.