decision-log

Records architectural decisions as numbered ADR markdown files with context, options, and consequences.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill decision-log-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/decision-log
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill decision-log-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architectural and design decisions made during development are forgotten between sessions, causing repeated re-litigation of the same trade-offs and inconsistent choices. This Skill captures the reasoning behind every non-trivial decision in a searchable, chronological ADR log. ## Core Features & Use Cases - Structured ADR Creation: Generates sequentially numbered ADR files (e.g., 003-jwt-refresh-rotation.md) from a template covering context, options considered, decision, and consequences. - Decision Discovery: Searches existing ADRs by keyword or tag before deciding, and links superseding decisions both ways to preserve history. - Index Maintenance: Updates a central INDEX.md with chronological and tag-based tables so decisions stay searchable across sessions. - Use Case: When choosing between JWT refresh rotation and long-lived tokens for a mobile app, invoke this Skill to check prior ADRs, frame the trade-offs, write ADR-008, and register it in the index for future sessions to reuse. ## Quick Start Log an architectural decision record for choosing PostgreSQL over MongoDB for the health data store, including the options considered and trade-offs.

Frequently Asked Questions about decision-log

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

FAQPage Schema
How do I create an architecture decision record (ADR)?▼

Copy the ADR template, assign the next sequential 3-digit number, and fill in status, date, context, decision, options considered, and consequences. Then register the new entry in the chronological and tag tables of INDEX.md.

When should I write an ADR versus skip it?▼

Write an ADR when choosing between approaches, adopting libraries, changing project-wide conventions, defining cross-repo contracts, or reversing prior decisions. Skip it for local micro-choices, established conventions, and trivial defaults.

How do I handle a decision that replaces an older ADR?▼

Never edit the old ADR's content. Create a new ADR that supersedes it, set the old one's status to "Superseded by NNN", and link both files to each other so the full decision history remains traceable.

Is an ADR log useful for a solo developer?▼

Yes. The ADR log serves future-you and AI assistant sessions by recording why trade-offs were made, preventing the same decision from being re-litigated months later. Keep each ADR to about one page.

What are common ADR mistakes to avoid?▼

Avoid recording only the decision without options considered, vague justifications like "A is better" without quantified criteria, editing old ADRs instead of superseding, and tagging everything as general, which destroys searchability.