ywc-adr

Capture, list, and curate Architecture Decision Records as standardized Markdown files.

8|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ywc-adr
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-adr
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of architectural decisions being lost or forgotten after a planning session, ensuring that hard-to-reverse trade-offs are documented for future reference.

Core Features & Use Cases

  • Decision Capture: Records architectural choices with context, alternatives, and consequences in a standardized format.
  • Lifecycle Management: Supports superseding outdated decisions and deprecating those that no longer apply to the codebase.
  • Contextual Retrieval: Allows filtering and loading relevant ADRs on-demand to inform new development or reviews.

Quick Start

Ask the agent to record the current architectural decision as an ADR to ensure it is documented for the team.

Frequently Asked Questions about ywc-adr

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

FAQPage Schema
How do I document architectural decisions to prevent them from being forgotten?

Architecture Decision Records capture architectural choices with context, alternatives, and consequences in standardized Markdown files, ensuring hard-to-reverse trade-offs are persisted for long-term maintainability and team reference.

What is the best way to manage the lifecycle of outdated architectural decisions?

Architecture Decision Records support lifecycle management by allowing you to supersede outdated decisions and deprecate those that no longer apply to the codebase, maintaining accurate point-in-time provenance and status tracking.

When do I need to start using Architecture Decision Records in my software engineering workflow?

You need Architecture Decision Records when architectural trade-offs must be persisted for long-term maintainability, specifically to capture point-in-time provenance, alternative analysis, and status tracking of technical constraints.

How do I record a current architectural choice as an ADR for my team?

You can ask the agent to record the current architectural decision as an ADR, which captures the choice in an immutable-ish Markdown file with standardized context, alternatives, and consequences for team documentation.

Can I filter and load relevant ADRs on-demand to inform new development?

Contextual retrieval allows filtering and loading relevant Architecture Decision Records on-demand, enabling you to pull specific architectural constraints and historical context to inform new development or code reviews.