skills.rest
carlkibler
carlkiblerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decision-log

Document product and engineering decisions with rationale and alternatives in markdown.

3|Updated Mar 27, 2026
Search Tags:#documentation#knowledge management#decision#engineering#product
One-click install
npx skills add https://github.com/carlkibler/agent-skills --skill decision-log-carlkibler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/carlkibler/agent-skills/tree/main/skills/decision-log
Command: npx skills add https://github.com/carlkibler/agent-skills --skill decision-log-carlkibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically capture and organize key product and technical decisions, preventing knowledge loss and ensuring consistent communication.

Core Features & Use Cases

  • Decision Recording: Promptly log decision details, context, and alternatives at the moment they are made.
  • Structured Documentation: Generate standard markdown entries for easy review and updates.
  • Use Case: A development team uses this Skill to document architectural choices, capturing reasons and future revisit triggers, ensuring that new team members understand key rationale.

Quick Start

Log a new decision by providing the decision summary, context, and options considered directly via the command prompt.

Frequently Asked Questions about decision-log

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

FAQPage Schema
How do I document engineering decisions to prevent knowledge loss?▼

To document engineering decisions and prevent knowledge loss, you can systematically log decision summaries, context, and alternatives at the moment they are made. This maintains institutional knowledge and ensures new team members understand the rationale behind key choices.

What is the best way to track architectural choices for future revisit planning?▼

Tracking architectural choices for future revisit planning involves capturing decision details, alternatives, and specific revisit triggers. This structured documentation approach ensures teams can consistently review and update technical decisions when necessary.

How do I generate standard markdown entries for product decisions?▼

You can generate standard markdown entries for product decisions by providing the decision summary, context, and options considered directly via the command prompt. This enforces structured formats for easy review and updates.

Does this decision logging process work with version control workflows?▼

Yes, this decision logging process supports integration with version control workflows. It streamlines the process of capturing product and engineering decisions, ensuring traceability and consistent communication across your development team.

Can I use this to record alternatives and rationale for technical decisions?▼

Yes, you can use this to record alternatives and rationale for technical decisions. It enforces structured documentation by prompting you to capture the context, options considered, and specific reasons behind architectural choices.

Related Skills

Explore More Software Engineering Skills→
arturgomsarturgoms

Journal Skill

Manage daily journal entries and generate weekly therapy summaries via Python script.

Community
Intermediate
xshi19xshi19

git-conventions

Enforce Git commit message standards, pre-commit checks, and release workflows.

Community
Intermediate
damidanidamidani

create-justification

Generate structured Markdown justification files with frontmatter and formatted titles.

Community
Basic
hgflimahgflima
1

documentation-and-adrs

Create and manage architectural decision records using markdown templates.

Community
Advanced