decision-log

Document project decisions with context, alternatives, and rationale in Markdown.

3|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/broomva/skills --skill decision-log-broomva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/broomva/skills/tree/main/skills/strategy/decision-log
Command: npx skills add https://github.com/broomva/skills --skill decision-log-broomva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of undocumented project history, ensuring that the rationale, alternatives, and consequences of important choices are preserved for future reference.

Core Features & Use Cases

  • Structured Documentation: Automatically formats decisions into a standardized template including context, alternatives, and reversibility.
  • Vault Integration: Links decisions directly to project documentation and maintains a searchable record.
  • Use Case: When a team debates between two technical architectures, use this skill to record the chosen path, the rejected alternatives, and the specific trade-offs accepted to prevent future confusion.

Quick Start

Ask the assistant to log a decision regarding the new database migration strategy including the alternatives considered and the rationale for the final choice.

Frequently Asked Questions about decision-log

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

FAQPage Schema
How do I document project decisions and track the rationale behind technical choices?

Recording project decisions involves documenting the context, alternatives, and rationale in a standardized Markdown format. This preserves the history of important choices and prevents future confusion over accepted trade-offs and rejected technical architectures.

What is an ADR and when should I use architecture decision records?

An ADR, or architecture decision record, is a standardized document used to capture the context, alternatives, and consequences of a technical choice. You should use ADRs when a team debates between technical architectures to ensure comprehensive and searchable historical records.

How do I log a database migration strategy including alternatives considered and trade-offs accepted?

To log a database migration strategy, you input the decision-making criteria into a structured template. This records the chosen path, rejected alternatives, and specific trade-offs, linking the decision directly to your local vault for long-term knowledge management.

Does this decision logging method work with a local Markdown vault?

Yes, this method integrates directly with a local vault by linking decision records to project-specific documentation. It requires structured input of decision-making criteria to maintain comprehensive and searchable historical records within your local Markdown files.

What is the best way to maintain searchable historical records of project strategy?

The best way to maintain searchable project strategy records is to archive critical decisions in a standardized Markdown format. Documenting the rationale and reversibility of choices facilitates long-term knowledge management and prevents undocumented project history.