ss-sdd-maintaining-adrs

Extract ADR-worthy decisions from a spec and write new ADR files.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-maintaining-adrs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-sdd-maintaining-adrs
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/spec-driven-development/ss-sdd-maintaining-adrs
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-maintaining-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams keep architectural documentation aligned with evolving specs by turning ADR-worthy decisions into properly formatted ADR records without duplicating existing ones.

Core Features & Use Cases

  • Extracts ADR-worthy decisions from a spec: focuses on architectural choices where the reasoning would otherwise be re-litigated by future engineers.
  • Avoids duplicates and handles supersession: compares candidates against existing ADRs to skip already-covered decisions or supersede them appropriately.
  • Writes ADRs in a locked, consistent format: generates new ADR files using the required numbering and structure, or returns 0 when nothing qualifies.

Quick Start

Dispatch the ss-sdd-maintaining-adrs skill with your SPEC_PATH, the ADR_DIR containing existing ADRs, and the EXISTING_ADRS list to have it create any missing ADRs in the locked format.

Frequently Asked Questions about ss-sdd-maintaining-adrs

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

FAQPage Schema
How do I automatically extract architecture decision records from a spec?

You can automatically extract ADR-worthy decisions from a spec by dispatching a subagent that reads the spec, identifies architectural choices, and generates new ADR files in a locked format to maintain architecture documentation.

How do I avoid duplicate ADRs when generating new architecture decision records?

To avoid duplicate ADRs, the extraction process reads all existing ADR files in the target directory, compares candidates against them, and skips already-covered decisions or marks them as superseded appropriately.

What is the best way to maintain architecture documentation during spec-driven development?

Maintaining architecture documentation during spec-driven development involves automatically capturing ADR-worthy decisions from evolving specs and writing them into sequentially numbered, locked-format files to ensure software governance.

How do I format new architecture decision records to maintain sequential numbering?

You format new records by reading all existing ADR files in the directory to determine the next sequential ADR number, then writing the extracted decisions using the required locked structure and numbering scheme.

What happens to architectural decisions in a spec that have already been documented?

Architectural decisions in a spec that have already been documented are skipped to avoid duplicates, or superseded appropriately, with the skipped and superseded decisions reported back to the coordinator.