adr

Draft architectural decision records with alternatives, tradeoffs, and evidence trails.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/remiboivin021/synexis --skill adr-remiboivin021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/remiboivin021/synexis/tree/main/.agents/skills/adr
Command: npx skills add https://github.com/remiboivin021/synexis --skill adr-remiboivin021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate formal ADRs that capture architectural decisions, boundaries, and governance constraints, ensuring decisions are traceable and reviewable across handoffs.

Core Features & Use Cases

  • Atomic ADR drafting for each decision boundary, aligned with repository governance.
  • Evidence mapping to concrete files, contracts, and existing behavior to avoid drift.
  • Open questions handling to capture uncertainties and future changes.

Quick Start

Identify the change triggers and generate a complete ADR draft following the template, awaiting approval to publish.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document architectural decisions to ensure traceability across team handoffs?

Architectural decision records capture decisions, boundaries, and governance constraints to ensure traceability across handoffs. This Skill drafts ADRs mapping evidence to concrete files and contracts, preventing documentation drift during team transitions.

What is the best way to structure an ADR with alternatives and tradeoff comparisons?

A complete ADR provides 2-3 alternatives, compares tradeoffs, and maps each option to concrete contracts and pipelines. The draft includes validation, migration, rollback procedures, and an auditable evidence trail for formal review.

How do I generate an ADR draft that includes migration and rollback boundaries?

Generating an ADR draft involves identifying change triggers and framing them within a defined scope. The template-complete output includes validation steps, migration and rollback boundaries, and open questions handling to capture future uncertainties.

When do I need an architectural decision record for repository governance?

You need an architectural decision record when high-impact architectural decisions affect repository governance and require formal approval. The ADR aligns the decision boundary with existing governance constraints before publishing.

How does evidence mapping work when drafting formal architecture documentation?

Evidence mapping connects the architectural decision to concrete files, contracts, and existing system behavior. This mechanism avoids documentation drift by anchoring the ADR draft to verifiable system artifacts for review.

Can I capture open questions and uncertainties in a formal architectural decision record?

Capturing open questions in an architectural decision record documents uncertainties and future changes. The ADR template includes an open questions handling section to track unresolved issues alongside the core decision, alternatives, and tradeoffs.