decide-adr

Record asynchronous architecture decisions in a structured ADR format.

89|32|Updated May 28, 2026
One-click install
npx skills add https://github.com/genkovich/sdd --skill decide-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decide-adr
Source: https://github.com/genkovich/sdd/tree/main/skills/decide-adr
Command: npx skills add https://github.com/genkovich/sdd --skill decide-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The decide-adr Skill addresses the challenge of capturing post-hoc architecture decisions that occur outside of the synchronous design phase, ensuring they are properly documented, reviewed, and integrated into the project's documentation.

Core Features & Use Cases

  • Post-hoc Decision Recording: Capture decisions made asynchronously, such as during code reviews or on-the-fly discussions.
  • Decision Review Flow: Supports a Proposed → Accepted review flow for decisions that require sign-off.
  • Compliance and Traceability: Ensures decisions are documented in a standardized format and linked to the relevant project documentation.
  • Use Case: Use this Skill when a decision is made in a chat, on a whiteboard, or during a review gate, and you need to document it as a MADR ADR.

Quick Start

To record a decision, use the command: /sdd:decide-adr <slug> <title>

Frequently Asked Questions about decide-adr

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

FAQPage Schema
How do I document asynchronous architecture decisions made outside of design sessions?

To document asynchronous architecture decisions, you can capture them post-hoc using a structured format. This Skill records decisions made during code reviews or on-the-fly discussions, ensuring they are properly documented and linked to existing project documentation.

What is the MADR format for recording project architecture decisions?

The MADR format for recording project architecture decisions is a standardized structure used to capture decisions with context and traceability. This approach supports a proposed to accepted review flow, ensuring compliance for asynchronous decisions.

How do I record an architecture decision from a code review or chat discussion?

To record an architecture decision from a code review or chat, use the command to create a decision record with a slug and title. This captures the asynchronous decision and integrates it into your project documentation for review and acceptance.

Can I use a proposed to accepted review workflow for project documentation decisions?

Yes, you can use a proposed to accepted review workflow for project documentation decisions. This Skill supports a decision review flow, allowing stakeholders to sign off on asynchronous architecture decisions before they are finalized.

Do I need access to the project feature directory to record architecture decisions?

Yes, you need access to the project feature directory and decision context to record architecture decisions. This access allows the Skill to integrate the documented decisions directly into your existing project documentation structure.

What is the best way to ensure compliance and traceability for post-hoc architecture decisions?

The best way to ensure compliance and traceability for post-hoc architecture decisions is to document them in a standardized format. This Skill links asynchronous decisions to relevant project documentation, maintaining a clear review and acceptance trail.