log-decision

Drafts structured Decision Record documents capturing architectural trade-offs and technology choices.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/azborgonovo/ai-skills --skill log-decision-azborgonovo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: log-decision
Source: https://github.com/azborgonovo/ai-skills/tree/main/skills/decisions/log-decision
Command: npx skills add https://github.com/azborgonovo/ai-skills --skill log-decision-azborgonovo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Significant technical decisions get made in conversations and then forgotten, leaving future readers with no record of why a choice was made. This Skill captures the reasoning behind hard-to-reverse decisions in a structured, numbered Decision Record (DR) file that outlives the conversation. ## Core Features & Use Cases - Guided information gathering: Asks one topic at a time for essentials (title, context, options, decision) and optional depth fields (forces, consequences, metadata like status and decision-makers). - Automatic DR file management: Locates or creates the DR directory (docs/decisions/, adr/, or .decisions/), assigns the next sequence number, and derives a kebab-case filename like DR-0003-use-postgresql-as-primary-datastore.md. - Template-based writing with supersede handling: Fills a Markdown template using the Y-Statement decision format, links related DRs, and updates superseded records with a back-reference. - Use Case: After a team debate about adopting PostgreSQL over MongoDB, invoke the skill to produce DR-0003-use-postgresql-as-primary-datastore.md with considered options, pros and cons, and the final Y-Statement decision. ## Quick Start Ask the AI to log a decision record for the database choice we just made, titled "Use PostgreSQL as primary datastore".

Frequently Asked Questions about log-decision

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

FAQPage Schema
How do I document an architecture decision record in a repository?▼

Invoke the skill with a decision title, then answer guided questions about context, considered options, and the final decision. It writes a numbered Markdown file such as DR-0003-use-postgresql-as-primary-datastore.md into docs/decisions/, adr/, or .decisions/.

What format does a Decision Record use?▼

The DR follows a Markdown template with sections for Context and Problem Statement, Forces and Constraints, Considered Options with pros and cons, and a Decision written as a Y-Statement. Optional frontmatter captures status, date, decision-makers, consulted, and informed parties.

When should I log a decision versus keep exploring options?▼

Log a DR only after the direction is settled and the decision is costly to reverse. If you are still weighing alternatives, the skill itself recommends using a decision-thinking skill first, then documenting the outcome afterward.

How are superseded decision records handled?▼

When a new DR has status superseded, the skill finds the older DR it replaces and adds a "Superseded by" note with a relative link to its More Information section. The new DR also references the old one, keeping the decision history traceable.

Where are decision record files stored and numbered?▼

The skill looks for an existing DR directory in priority order: docs/decisions/, then adr/, then .decisions/, creating docs/decisions/ if none exists. It scans DR-*.md files for the highest sequence number and assigns the next one, starting at 0001.