decision-log-guard

Name: decision-log-guard
Availability: InStock
Author: MithrilMan

Log significant project decisions with conflict checks and template-driven entries.

Updated Mar 12, 2026

Search Tags:#workflow #templates #documentation #governance #registry #decision-log

Ready to run

npx skills add https://github.com/MithrilMan/neomithril-ui --skill decision-log-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-log-guard
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/decision-log-guard
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill decision-log-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce disciplined documentation of significant decisions to keep teams aligned and reduce rework by ensuring decisions across product, architecture, API, data-model, security, dependency, and workflow domains are recorded in the central registry at docs/specs/DECISIONS.md.

Core Features & Use Cases

Decision registry: ensures every major choice is logged with context and tradeoffs in docs/specs/DECISIONS.md.
Conflict detection: compares new decisions against the existing index to surface potential contradictions before they are written.
Template-driven entries: guides users to create decision entries under docs/specs/decisions/entries using standardized filenames and structure.

Quick Start

Log a new decision by following the workflow prompts and creating the entry under docs/specs/decisions/entries.

Frequently Asked Questions about decision-log-guard

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

FAQPage Schema

How do I automatically log project architecture and API decisions to a central registry?▼

To log project decisions automatically, this Skill guides you through recording context, options, tradeoffs, and consequences into docs/specs/DECISIONS.md. It ensures every significant architecture, API, or workflow choice is documented using a standardized template.

What is a decision log governance workflow and when do I need it for documentation?▼

A decision log governance workflow enforces disciplined documentation of significant choices to keep teams aligned and reduce rework. You need it when managing product, security, or data-model decisions that require transparent tracking and validation across a project lifecycle.

Can I check new decisions for conflicts against an existing specs registry?▼

Yes, you can check new decisions for conflicts against the existing index. The Skill compares incoming choices against previously logged entries in docs/specs/DECISIONS.md to surface potential contradictions before they are officially recorded.

How to document tradeoffs and consequences for data-model and security choices?▼

To document tradeoffs and consequences, follow the workflow prompts to capture required context, final decision statements, and validation evidence. Entries are created under docs/specs/decisions/entries using prescribed templates with reverse chronological updates.

What is the best way to maintain a reverse chronological decision log in markdown?▼

The best way to maintain a reverse chronological decision log is to append new entries under docs/specs/decisions/entries and update the central index. This Skill automates that process, ensuring standardized filenames and structural consistency across all records.

Do I need a specific template format to record workflow and dependency decisions?▼

Yes, you need to use the prescribed template format to record workflow and dependency decisions. The Skill enforces a specific structure requiring context, options considered, final statements, consequences, status, validation, and evidence for every logged entry.