create-decision

Record architectural decisions as ADR files with context and consequences.

5|Updated Jul 25, 2025

Search Tags:#architecture #documentation #context #adr #decision #trade-offs #record-keeping

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-decision
Source: https://github.com/tomzx/agents/tree/main/skills/create-decision
Command: npx skills add https://github.com/tomzx/agents --skill create-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records architectural or implementation decisions as lightweight ADRs to preserve rationale and enable future review.

Core Features & Use Cases

Record decisions with context, options considered, chosen course, and consequences.
Save ADRs to a central location (e.g., .sdlc/knowledge/decisions/) with a consistent filename pattern NNNN-<slug>.md.
Facilitate onboarding, audits, and cross-team alignment by maintaining a living decision log.

Quick Start

Identify a concrete decision, describe context and options, choose a course of action, and save it as an ADR under .sdlc/knowledge/decisions/NNNN-<slug>.md.

Frequently Asked Questions about create-decision

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

FAQPage Schema

How do I document architectural decisions and trade-offs for future reference?▼

You document architectural decisions by creating formal ADRs that capture the problem, context, alternatives considered, trade-offs, and consequences to preserve rationale for future audits and onboarding.

What is an ADR and when do I need to write one?▼

An ADR is an architectural decision record used to document implementation choices, their context, and trade-offs. You need an ADR when a software project requires documented rationale for future reference, audits, or cross-team alignment.

How do I organize and save ADR files with a consistent naming pattern?▼

You save ADRs to a central location like .sdlc/knowledge/decisions/ using a consistent filename pattern of NNNN-<slug>.md, ensuring a stable file path under a dedicated repository for living decision logs.

Does this approach to decision record-keeping work for onboarding new team members?▼

Decision record-keeping works for onboarding by providing a living decision log that maintains documented context, chosen courses of action, and consequences, enabling new team members to understand past architectural rationale quickly.

What should be included in an architectural decision record?▼

An architectural decision record should include the problem description, decision context, alternatives considered, trade-offs, chosen course of action, and consequences to ensure comprehensive documentation for audits and reference.

Can I use ADRs to facilitate cross-team alignment on software architecture?▼

You can use ADRs to facilitate cross-team alignment by maintaining a shared, living decision log in a central repository that documents architectural context, trade-offs, and consequences for all teams to reference.