defining-adr

Automate ADR creation through a four-stage workflow with Design Briefs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ADR orchestration solves the friction of documenting architectural decisions by guiding scoping through Design Briefs and delegating drafting for high-quality records.

Core Features & Use Cases

  • Preparation and branch setup to isolate ADR work.
  • Scoping with Design Briefs to clarify context, decisions, and trade-offs.
  • Execution: drafting and auditing of the ADR, ensuring alignment with the brief.
  • Release: generating a PR-ready ADR document and facilitating reviews.

Quick Start

Start by activating the ADR defining skill and follow the four-step workflow to scope decisions and draft the ADR.

Frequently Asked Questions about defining-adr

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

FAQPage Schema
How do I create an Architecture Decision Record from a design brief?

To create an Architecture Decision Record (ADR) from a design brief, the workflow guides you through scoping context and trade-offs, then drafts the ADR while ensuring alignment with the original brief.

What is the best way to document system architecture trade-offs for a pull request?

Documenting system architecture trade-offs for a pull request is best handled by generating an audit-ready ADR document that captures design decisions and facilitates formal code reviews.

How does an ADR workflow handle the scoping and release of architectural decisions?

An ADR workflow handles scoping and release by progressing through preparation, scoping with design briefs, execution of the draft, and releasing a PR-ready document for governance review.

Can I use design briefs to enforce governance and auditing for architecture decisions?

Yes, you can use design briefs to enforce governance and auditing for architecture decisions by clarifying context and trade-offs before drafting, ensuring the final record is audit-ready and aligned with project requirements.

When do I need a formal Architecture Decision Record for my software project?

You need a formal Architecture Decision Record for your software project during system changes or team design sessions where design trade-offs must be explicitly captured, reviewed, and audited.

Does the ADR drafting process integrate with branch setup and PR management?

Yes, the ADR drafting process integrates with branch setup and PR management by isolating architecture work in a dedicated branch and producing a release-ready document for pull request reviews.