decision

Record architectural and business logic decisions to DECISIONS.md with ADR/BIZ templates.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill decision-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/decision-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill decision-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture architectural (ADR) and business logic (BIZ) decisions in a single DECISIONS.md file, preserving rationale and enabling quick future reference.

Core Features & Use Cases

  • Records ADR and BIZ decisions with a consistent format
  • Organizes entries by date and a single numbering sequence for traceability
  • Provides templates and a lightweight workflow for adding new decisions and preserving history
  • Supports easy collaboration and governance around architectural and business logic choices

Quick Start

Add a new ADR- or BIZ- entry to DECISIONS.md following the template, then commit.

Frequently Asked Questions about decision

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

FAQPage Schema
What is an ADR and how does it fit into software architecture governance?

An Architectural Decision Record (ADR) captures the rationale behind software architecture choices. This skill logs ADRs and business logic decisions into DECISIONS.md, preserving historical context for project governance and quick future reference.

How do I record architectural and business logic decisions in a single log?

To record architectural and business logic decisions, add an ADR or BIZ entry to DECISIONS.md following the provided template. The skill applies a consistent format, numbering sequence, and date for traceable decision logging.

Can I use a markdown file to track both ADR and BIZ decisions together?

Yes, you can track both ADR and BIZ decisions together in a DECISIONS.md file. This skill provides standardized templates and a lightweight workflow to organize entries by date and a single numbering sequence for traceability.

What is the best way to maintain a historical record of system design decisions?

The best way to maintain a historical record of system design decisions is using a standardized ADR format. This skill provides a lightweight workflow for numbering, dating, and committing entries to DECISIONS.md to preserve rationale.

Does this approach to decision logging require any specific dependencies or components?

No specific dependencies or components are required to log decisions. The skill uses a lightweight workflow to format entries in DECISIONS.md, making it easy to implement in any software architecture or project governance environment.