decision-logger

Name: decision-logger
Availability: InStock
Author: timequity

Log architectural decisions as ADR entries to docs/DECISIONS.md.

6|Updated Dec 7, 2025

Search Tags:#architecture #adr #decision

Ready to run

npx skills add https://github.com/timequity/plugins --skill decision-logger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-logger
Source: https://github.com/timequity/plugins/tree/main/craft-coder/decision-logger
Command: npx skills add https://github.com/timequity/plugins --skill decision-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures architectural decisions in ADR format to keep project history.

Core Features & Use Cases

ADR Creation: Create ADR entries with metadata
ADR Templates: Standard ADR structure
Integration: Works with /craft and /why commands

Quick Start

Dispatch a decision and log to docs/DECISIONS.md.

Frequently Asked Questions about decision-logger

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

FAQPage Schema

How do I log architectural decisions in ADR format?▼

ADR (Architecture Decision Record) format logs architectural decisions with structured metadata including context, decision rationale, consequences, and alternatives. This Skill automates ADR creation with automatic numbering and appends entries to docs/DECISIONS.md, capturing trade-offs from technology stack selections and library choices.

When should I document architectural decisions?▼

Document architectural decisions when selecting technology stacks, choosing libraries, defining project structure, or making significant trade-offs. ADRs preserve project history and reasoning, helping teams understand why past decisions were made and their consequences for future choices.

Can I integrate ADR logging into my development workflow?▼

Yes. This Skill integrates with /craft and /why commands, automatically capturing decisions during those workflows and logging them as ADR entries with consistent structure, metadata, and automatic numbering in your project documentation.

What information does an ADR capture?▼

An ADR captures context (situation and constraints), the decision made, consequences (benefits and drawbacks), and alternatives considered. This Skill generates ADRs with automatic numbering and appends them to docs/DECISIONS.md for persistent project history.

Do I need a specific template to create ADRs?▼

This Skill provides standard ADR templates that structure entries consistently with required sections: context, decision, consequences, and alternatives. The template ensures uniform documentation across all architectural decisions in your project.