665,000+ skills indexed

Explore all skills by this author →

Verified:GitHub

decision-log

Manage project decisions in notes/DECISIONS.md with unique dcn-xxxx identifiers.

Updated Dec 19, 2025

Search Tags:#project management #documentation #decisions #knowledge management #logging

One-click install

npx skills add https://github.com/a3lem/my-claude-plugins --skill decision-log-a3lem

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/a3lem/my-claude-plugins/tree/main/plugins/project-notes/skills/decision-log
Command: npx skills add https://github.com/a3lem/my-claude-plugins --skill decision-log-a3lem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of recording and accessing critical project decisions, ensuring that architectural choices, design agreements, and team consensus are documented and easily retrievable.

Core Features & Use Cases

Decision Logging: Records decisions with unique dcn-xxxx identifiers in notes/DECISIONS.md.
Status Tracking: Allows for marking decisions as reversed or superseded.
Reference Linking: Supports tagging and linking to related notes or journal entries.
Use Case: When the team agrees on a new caching strategy, use this Skill to log it with a unique ID and relevant tags, making it easy to find later and reference in future discussions.

Quick Start

Log a new decision to use Memorystore instead of self-hosted Redis, tagging it as infra.

Frequently Asked Questions about decision-log

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

FAQPage Schema

How do I log project decisions and architectural choices for easy retrieval?▼

You log project decisions by recording architectural choices and team agreements in a structured file using unique identifiers and tags. This ensures critical design decisions are documented and easily retrievable for future reference.

What is the best way to track when a design decision is reversed or superseded?▼

Tracking reversed or superseded design decisions is handled by updating the status of logged entries. You can mark previous architectural choices as reversed or superseded by newer decisions to maintain an accurate historical record.

How does linking and tagging work for knowledge management of team agreements?▼

Linking and tagging for knowledge management works by assigning tags and connecting references to related notes or journal entries. This mechanism enables efficient retrieval of past team agreements through linked documentation.

Can I use markdown documentation to assign unique identifiers to project decisions?▼

Yes, you can use markdown documentation to assign unique identifiers to project decisions. The system automatically assigns identifiers to architectural choices and design decisions logged within the markdown file structure.

Do I need any specific dependencies or setup to start logging architectural decisions?▼

You do not need any specific dependencies to start logging architectural decisions. The system operates without external requirements, storing design decisions directly within your project's markdown notes file.

Related Skills

Explore More Product & Management Skills→

docs-writer

Write and edit Markdown documentation following Gemini CLI project standards.

remembering-conversations

Search past conversations to surface relevant decisions and patterns.

Obsidian Automation

Automate Obsidian note creation, linking, and template-driven knowledge management.

architecture

Guides requirements analysis, trade-off evaluation, and ADR documentation for architectural decisions.