trails-adrs

Document Trails ADRs with context, decisions, and consequences across CLI, MCP, and HTTP surfaces.

4|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/outfitter-dev/trails --skill trails-adrs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trails-adrs
Source: https://github.com/outfitter-dev/trails/tree/main/.claude/skills/trails-adrs
Command: npx skills add https://github.com/outfitter-dev/trails --skill trails-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

ADRs document the significant design decisions behind Trails and provide a single source of truth for decisions, their context, options considered, and consequences.

Core Features & Use Cases

  • Create new ADRs and drafts to capture decisions early
  • Promote drafts to numbered ADRs and update cross-references and index entries
  • Update metadata (title, slug, status, id) and reconstruct the ADRs hierarchy while preserving history
  • Maintain a consistently generated ADR decision map and drafts index for governance

Quick Start

Create a new ADR draft with a descriptive title, then promote it when it is ready to be accepted.

Frequently Asked Questions about trails-adrs

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

FAQPage Schema
How do I document architecture decisions and track their context and consequences?▼

Architecture decision records capture design choices, context, and consequences as structured documents. This Skill authors ADRs with enforced frontmatter completeness to maintain a single source of truth for governance across CLI, MCP, and HTTP surfaces.

What's the best way to promote an ADR draft to a numbered entry without breaking cross-references?▼

Promoting ADR drafts to numbered entries automatically rewrites cross-references and updates the index. The tooling reconstructs the ADRs hierarchy while preserving history, ensuring the decision map and drafts index stay consistent.

How do I maintain an ADR index and decision map for governance across multiple surfaces?▼

ADR governance requires a consistently generated decision map and drafts index. This Skill enforces frontmatter completeness and provides tooling to manage numbered entries and drafts across CLI, MCP, and HTTP surfaces.

Can I rename or renumber existing ADRs while preserving their history?▼

Renaming or renumbering ADRs updates metadata like title, slug, status, and id while reconstructing the hierarchy. The tooling preserves history and rewrites cross-references to keep the decision map consistent.

When do I need to use ADRs for architecture governance instead of regular documentation?▼

ADRs are needed when documenting significant design decisions that require governance. Unlike regular documentation, ADRs capture options considered, context, and consequences, providing a single source of truth for decision tracking.

Why does my ADR cross-reference break after renumbering entries?▼

Broken cross-references occur when renumbering ADRs without updating links. This Skill provides tooling to automatically rewrite cross-references and reconstruct the ADRs hierarchy, preventing index inconsistency.