decision-log

Create ADR-formatted decision records and update the decision index.

5|1|Updated Apr 10, 2026

Search Tags:#architecture #documentation #adr #governance #engineering #decision log

Ready to run

npx skills add https://github.com/garethrhughes/fragile --skill decision-log-garethrhughes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/decision-log
Command: npx skills add https://github.com/garethrhughes/fragile --skill decision-log-garethrhughes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns important engineering choices into a durable, searchable record so the team can remember what was decided, why it was decided, and where to find it later.

Core Features & Use Cases

ADR Creation: Drafts architectural decision records in the project’s required format.
Decision Tracking: Keeps a sequential decision history in docs/decisions/ and updates the index as new entries are added.
Use Case: When a team chooses a new framework, accepts a proposal, or settles a trade-off, this Skill records the decision consistently and makes it easy to review later.

Quick Start

Ask the AI to log the decision as an ADR in docs/decisions and update the decision index with the new entry.

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 architectural decision record for a new technology choice?▼

An architectural decision record (ADR) captures engineering choices like technology selections and design patterns in a durable, searchable Markdown format. This Skill drafts these entries in docs/decisions and synchronizes the index automatically.

What is the best way to maintain a traceable decision log for engineering trade-offs?▼

Maintaining a traceable decision log requires storing sequentially numbered ADR Markdown files in docs/decisions and synchronizing a README index. This Skill records accepted proposals and trade-offs consistently for future review.

Do I need a specific folder structure to track architecture decisions as ADRs?▼

You need a docs/decisions directory containing ADR-formatted Markdown files and a synchronized README.md index. This structure ensures your architecture decisions remain sequentially numbered and searchable.

When should I document engineering decisions using an ADR format?▼

You should document engineering decisions using an ADR format when settling technology choices, accepting proposals, or finalizing configuration and security trade-offs. This ensures the rationale behind design patterns is recorded durably.

Can I use this approach to track security and configuration decisions alongside design patterns?▼

Yes, this approach tracks security and configuration decisions alongside design patterns by capturing them as ADR-formatted Markdown entries. It applies to technology choices, accepted proposals, and trade-offs across engineering projects.