decision

Document architecture decisions and design patterns with ADR and DES templates.

1|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/asermax/claude-plugins --skill decision-asermax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/decision
Command: npx skills add https://github.com/asermax/claude-plugins --skill decision-asermax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document architecture decisions and design patterns to ensure traceability, consistency, and faster onboarding for software teams.

Core Features & Use Cases

  • ADRs and DES documentation templates for capturing context, decision, consequences, and alternatives.
  • Structured workflows for drafting, reviewing, and updating decisions with references to architecture and design indexes.
  • Reference materials and design pattern guidance to support repeatable decisions across projects.

Quick Start

Create your first ADR or DES entry by outlining the problem, the decision, the alternatives considered, and the consequences.

Frequently Asked Questions about decision

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

FAQPage Schema
What is an ADR and when do I need to document architecture decisions?

An ADR captures context, decisions, alternatives, and consequences for software architecture. You need ADR documentation when establishing traceability and consistency for design patterns across project features to accelerate team onboarding.

How do I write an ADR or DES entry for a software project?

To write an ADR or DES entry, outline the problem, state the decision, list alternatives considered, and describe consequences. Structured workflows provide templates and guidance prompts to draft, review, classify, and update decision indexes.

How do I maintain consistency across architecture decisions and design patterns?

Maintain consistency across architecture decisions by using structured workflows to review and update entries with references to architecture and design indexes, ensuring repeatable decisions across projects through provided reference materials and design pattern guidance.

Can I use this to document design patterns alongside architecture decisions?

Yes, you can document design patterns alongside architecture decisions. The system supports both ADR and DES documentation templates, capturing context and consequences while providing reference materials to support repeatable design pattern decisions.

What's the best way to structure decision records for faster team onboarding?

The best way to structure decision records is using standardized ADR and DES templates that capture context, decision, alternatives, and consequences, linked to centralized architecture and design indexes for consistent traceability and faster onboarding.

Do I need any specific tools or dependencies to start documenting architecture decisions?

No specific tools or dependencies are required to start documenting architecture decisions. You can create your first ADR or DES entry by outlining the problem, decision, alternatives, and consequences using the provided templates and workflow steps.