skills.rest
vincenttresno
vincenttresnoCOMMUNITY
Explore all skills by this author →
GitHub

decision-documentation

Document critical decisions from Claude Code sessions into centralized, searchable records.

Updated Aug 23, 2026
Search Tags:#templates#recall#decision#document#knowledge-graph#decision-log
One-click install
npx skills add https://github.com/vincenttresno/luke-brain-template --skill decision-documentation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-documentation
Source: https://github.com/vincenttresno/luke-brain-template/tree/main/.claude/skills/decision-documentation
Command: npx skills add https://github.com/vincenttresno/luke-brain-template --skill decision-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Capture and organize important decisions from Claude Code sessions into a centralized, searchable record that preserves rationale and context for future reference.

Core Features & Use Cases

  • Automatic and manual decision capture triggered by keywords or explicit requests.
  • Structured templates and consistent storage locations across business, technical, and session contexts.
  • Easy recall and context linking via memory graphs, indexing, and /recall commands to surface relevant decisions.

Quick Start

Trigger a decision capture by stating the decision clearly and providing alternatives, rationale, and next steps.

Frequently Asked Questions about decision-documentation

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

FAQPage Schema
How do I document decisions made during Claude Code sessions for future recall?▼

To document decisions during Claude Code sessions, state the decision clearly with alternatives, rationale, and next steps to trigger structured templates that store entries in a centralized, searchable record for fast recall.

What is a decision log and how does it preserve context for technical projects?▼

A decision log preserves context by capturing critical decisions and their rationale into structured templates with full, quick, and technical variants, linking related context through memory graphs and indexing for quick recall.

Can I automatically capture decisions without manually requesting documentation each time?▼

Yes, automatic decision capture triggers when decision keywords are spoken during a Claude Code session or when a user explicitly requests documentation, applying a structured workflow without requiring manual log entries.

Does this decision documentation approach support different template types for technical and business contexts?▼

Yes, the decision documentation workflow enforces structured templates with full, quick, and technical variants, ensuring consistent storage locations across business, technical, and session-specific contexts.

What is the best way to maintain a searchable knowledge graph of project decisions?▼

The best way to maintain a searchable knowledge graph is to document critical decisions into centralized storage locations with structured templates, enabling recall via memory graphs and indexing to surface relevant decisions on demand.

Related Skills

Explore More Product & Management Skills→
arbisoftarbisoft
4

knowledge-ops

Centralize knowledge management across local files, MCP memory, vector stores, and Git repositories.

Official
Advanced
KKenny0KKenny0
2

recall

Extract recent progress, decisions, risks, and open questions from project vault data.

Community
Advanced
tttoltttol

agent-memory

Store structured memories with frontmatter metadata for cross-session recall.

Community
Advanced
Sake-TeamSake-Team

architecture-decision-records

Capture and manage architectural decision records with structured ADR logs.

Official
Advanced