skills.rest
seankao31
seankao31COMMUNITY
Explore all skills by this author →
GitHub

capture-decisions

Capture decisions and rationale from active sessions into ADR and MEMORY.md entries.

Updated Apr 10, 2026
Search Tags:#documentation#decisions#adr#memory#capture#engineering-workflow
One-click install
npx skills add https://github.com/seankao31/dotfiles --skill capture-decisions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture-decisions
Source: https://github.com/seankao31/dotfiles/tree/main/agent-config/skills/capture-decisions
Command: npx skills add https://github.com/seankao31/dotfiles --skill capture-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures the context, decisions, and rationale from ongoing sessions so nothing important is lost when a session ends.

Core Features & Use Cases

  • Inline decision capture: Attaches notes and inline comments at decision points in code or discussions.
  • ADR and MEMORY integration: Creates ADR-like and MEMORY.md entries to document choices and context for future sessions.
  • Structured guidance: Provides a reproducible workflow to triage decisions into inline, ADR, and memory artifacts.

Quick Start

Begin capturing decisions while the session is active to preserve context and rationale for future work.

Frequently Asked Questions about capture-decisions

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

FAQPage Schema
How do I capture session decisions and design rationale during engineering discussions?▼

To capture session decisions and design rationale, you can attach inline notes at decision points and generate ADR-style entries. This preserves context from active engineering discussions and debugging sessions for future reference.

What is the best way to document architectural decisions so context is not lost when a session ends?▼

Documenting architectural decisions is best handled by triaging choices into inline notes, ADR-style documentation, and MEMORY.md entries. This structured workflow prevents the loss of context and rationale after a session concludes.

Can I use MEMORY.md integration to save decisions from an active debugging session?▼

Yes, MEMORY.md integration is supported to save decisions from an active debugging session. The workflow captures choices and context, creating memory artifacts that document rationale for future work sessions.

Do I need a specific framework to create ADR-style documentation for planning wrap-ups?▼

No specific framework is required to create ADR-style documentation for planning wrap-ups. The workflow provides structured guidance to reproducibly triage decisions into inline notes, ADRs, and memory artifacts without external dependencies.

When do I need to use inline decision notes versus ADR entries?▼

You need inline decision notes for attaching comments directly at decision points in code or discussions, while ADR entries document broader architectural choices. The workflow triages decisions into the appropriate artifact type.

Related Skills

Explore More Software Engineering Skills→
Jerry-Z07Jerry-Z07
21

start

Initialize AI development sessions by loading workflow guides, git status, and project guidelines.

Community
Intermediate
tejovanthntejovanthn
1

architecture-decision-records

Create standardized Architecture Decision Records with YAML frontmatter and structured sections.

Community
Intermediate
semicolon-devteamsemicolon-devteam

summarize-meeting

Summarize STT transcripts and meeting notes into discussion and decision summaries.

Official
Advanced
Partners-in-BizPartners-in-Biz

documentation-and-adrs

Document architectural decisions and design rationales in Markdown ADRs with YAML frontmatter.

Community
Advanced