record-decision

Record architectural decisions to .claude/docs/DECISIONS.md with unique identifiers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/emirrtopaloglu/claude-code-virtuoso --skill record-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-decision
Source: https://github.com/emirrtopaloglu/claude-code-virtuoso/tree/main/.claude/skills/record-decision
Command: npx skills add https://github.com/emirrtopaloglu/claude-code-virtuoso --skill record-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record critical architectural or product decisions to long-term memory for future reference and ADR traceability.

Core Features & Use Cases

  • Centralized decision logging to .claude/docs/DECISIONS.md with unique identifiers.
  • Duplicate detection and context preservation for team alignment.
  • Optional ADR generation and linkage to existing decisions for auditability.

Quick Start

Provide a decision summary to record a new ADR entry.

Frequently Asked Questions about record-decision

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

FAQPage Schema
How do I log architectural and product decisions for long-term memory?

You can log architectural and product decisions by providing a decision summary, which generates a unique identifier and automatically appends the record to .claude/docs/DECISIONS.md for durable memory and team alignment.

What is the best way to maintain an auditable ADR trail for my team?

Maintaining an auditable ADR trail is achieved by recording decisions with unique identifiers and optional ADR generation, linking new entries to existing records to preserve context and ensure traceability for team review.

Can I prevent duplicate decision records when logging multiple product scope changes?

Yes, duplicate detection is built into the decision logging process, ensuring that repeated entries are identified and preventing redundant records in your long-term memory log.

How does decision recording handle input validation for architectural changes?

Decision recording handles input validation by verifying the provided decision summary before generating an ID and appending the entry to DECISIONS.md, ensuring only valid architectural changes are logged.

When do I need to record decisions to a long-term memory log?

You need to record decisions to a long-term memory log when choices impact product scope, architecture, or monetization, requiring an auditable ADR trail for future reference and team alignment.

Does decision logging work without external dependencies for auditability?

Yes, decision logging works without external dependencies, using built-in input validation, ID generation, and automatic appending to .claude/docs/DECISIONS.md to ensure auditability and context preservation.