drafting-adr

Draft ADRs from design briefs with context, decision, and consequences.

Updated Aug 18, 2025
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill drafting-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drafting-adr
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/drafting-adr
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill drafting-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Drafting ADRs provides a structured way to capture architectural decisions, contexts, and rationales, while enabling rigorous self-audits to improve future maintainability.

Core Features & Use Cases

  • Create ADRs from design briefs, covering Context, Decision, and Consequences.
  • Self-audit ADR drafts against a checklist to ensure quality and traceability.
  • Use case: when documenting a major architectural change, generate a complete ADR with context, rationale, and trade-offs.

Quick Start

Draft an ADR by outlining the Design Brief, then run the self-audit step to validate it against the ADR audit checklist.

Frequently Asked Questions about drafting-adr

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 maintainers?

Document architectural decisions by drafting an ADR to capture context, decisions, and trade-offs. This provides a structured way to record rationale and ensure traceability for future maintainers across software projects.

What is the best way to self-audit an architecture decision record before finalizing it?

Self-audit an architecture decision record by validating the draft against a structured checklist. This ensures the ADR quality and traceability by verifying that context, rationale, and trade-offs are completely documented.

How do I write an ADR from a design brief?

Write an ADR from a design brief by outlining the brief and applying a structured template. This generates a complete record covering Context, Decision, and Consequences for the architectural change.

When do I need to create an ADR for a software project?

Create an ADR when documenting a major architectural change. You need this process to capture the context, rationale, and trade-offs of design decisions to improve future maintainability.

Does drafting an ADR require any specific dependencies or platforms?

Drafting an ADR requires no specific dependencies or platforms. It is applicable across software projects using a structured template, a self-audit checklist, and artifact generation to ensure traceability.