decision-log

Name: decision-log
Availability: InStock
Author: khairulariffinka

Log design decisions with rationale and impacted files in a structured manifest.

1|Updated Apr 12, 2026

Search Tags:#design #architecture #versioning #documentation #decision #traceability #rationale

Ready to run

npx skills add https://github.com/khairulariffinka/codexen --skill decision-log-khairulariffinka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/khairulariffinka/codexen/tree/main/core/skills/decision-log
Command: npx skills add https://github.com/khairulariffinka/codexen --skill decision-log-khairulariffinka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralized logging of design decisions, including the rationale and impacted files, to prevent knowledge loss and improve project traceability.

Core Features & Use Cases

Rationale capture: Record decisions with context and links to affected code files and modules.
Traceability: Build a history of decisions mapped to source files for audits and future changes.
Use Case: When redesigning a module, log the decision, the alternatives considered, the rationale, and the files touched.

Quick Start

Log a design decision with rationale and impacted files to establish traceability.

Frequently Asked Questions about decision-log

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

FAQPage Schema

How do I track design decisions and rationale in software projects?▼

To track design decisions, you log the decision, alternatives considered, and rationale in a structured manifest. This preserves project context by linking decisions to impacted files with timestamps for future audits and module redesigns.

What is the best way to maintain architecture traceability across code reviews?▼

Architecture traceability is maintained by logging design decisions with links to affected code files and modules. This builds a historical record mapped to source files, ensuring context is preserved during code reviews and future modifications.

How do I prevent knowledge loss when redesigning a software module?▼

Prevent knowledge loss during module redesigns by recording the design decision, alternatives considered, and rationale in a centralized log. Linking these entries to impacted files establishes clear traceability for future developers and audits.

Can I link historical context and impacted files to an architecture decision log?▼

Yes, you can link historical context and impacted files to an architecture decision log. The log stores decisions with timestamps, alternatives considered, rationale, and affected files in a structured manifest for full project traceability.

What should be included in design documentation for software architecture audits?▼

Design documentation for audits should include the design decision, alternatives considered, rationale, and impacted files. Storing these elements with timestamps in a structured manifest ensures comprehensive traceability across architecture discussions.

When do I need to log design decisions for software versioning and documentation?▼

You need to log design decisions during design sessions, code reviews, and architecture discussions. Capturing the rationale and impacted files at these points preserves context and maintains traceability for software versioning and documentation.