skills.rest
SpencerGoss
SpencerGossCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decision-log

Append architectural decisions with rationales and alternatives to DECISIONS.md.

Updated Apr 24, 2026
Search Tags:#architecture#documentation#decision#rationale#alternatives#decision-log
One-click install
npx skills add https://github.com/SpencerGoss/agent-engineering --skill decision-log-spencergoss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/SpencerGoss/agent-engineering/tree/main/decision-log
Command: npx skills add https://github.com/SpencerGoss/agent-engineering --skill decision-log-spencergoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions often get scattered and forgotten. This Skill provides a durable, append-only log that records decisions, the context, and the alternatives considered to prevent rework.

Core Features & Use Cases

  • Append-only DECISIONS.md logging with Status, Context, and Alternatives.
  • Link and trace decision history, including superseded decisions and reversals.
  • Revisit guidance to keep decisions current and aligned across sessions.

Quick Start

Create a new DECISIONS.md entry with a concise title, date, status, decision, context, and alternatives.

Frequently Asked Questions about decision-log

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

FAQPage Schema
How do I document architectural decisions and rationale in a markdown file?▼

Document architectural decisions by appending entries to a DECISIONS.md file, capturing the decision status, context, and alternatives considered to prevent rework and ensure long-term design choices are preserved across sessions.

What is the best way to track superseded architectural decisions and reversals?▼

Track superseded architectural decisions and reversals using an append-only DECISIONS.md log that links and traces decision history, ensuring past context and alternatives remain visible when new choices override old ones.

Do I need a specific file structure to log project design choices?▼

Yes, logging project design choices requires a DECISIONS.md file at the project root. The file supports standard sections like Status, Alternatives Considered, and Superseded history to maintain a durable record.

Can I record architectural context and alternatives across different team sessions?▼

Yes, you can record architectural context and alternatives across team sessions by maintaining an append-only DECISIONS.md log that preserves the rationale behind long-term design choices for all collaborators.

When should I create an entry in an architecture decision log?▼

Create an entry in an architecture decision log whenever selecting between multiple options or documenting a long-term design choice, ensuring the rationale and alternatives are captured before moving forward.

Related Skills

Explore More Software Engineering Skills→
jperezdelrealjperezdelreal

init-mode

Propose an AI squad roster and defer file creation until user confirmation.

Community
Advanced
timequitytimequity
6

decision-logger

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

Official
Intermediate
zircotezircote
3

documentation-standards

Audit Markdown documentation structure, formatting, links, and accessibility against defined standards.

Community
Advanced
bradtaylorsfbradtaylorsf
8

architecture-decisions

Generate Architecture Decision Records with a standardized template.

Community
Basic