{"enrichment":{"faq":[{"a":"architecture-decision-records helps you create ADRs by providing multiple templates and best practices. Start by identifying a significant technical choice, then document the context (problem statement), decision (what you chose), consequences (trade-offs and impacts), and alternatives considered. The skill supports standard MADR format and lightweight Y-statements, ensuring your team captures reasoning clearly and consistently for future reference.","q":"How to write architecture decision records?"},{"a":"architecture-decision-records offers several templates including the standard MADR (Markdown Architecture Decision Records) format and Y-statements. MADR typically includes Title, Status, Context, Decision, Consequences, and Alternatives sections. These templates help teams structure decisions uniformly, making it easier to review, compare, and understand the rationale behind architectural choices across your codebase.","q":"What is an ADR template for technical decisions?"},{"a":"architecture-decision-records guidance suggests writing ADRs for significant technical choices that affect system design, technology selection, or long-term maintainability. Focus on decisions with meaningful trade-offs, those impacting multiple teams, or choices that might be questioned later. Not every decision needs an ADR\u2014reserve them for architectural decisions that warrant documented reasoning and historical context.","q":"When should I write an ADR?"},{"a":"architecture-decision-records supports establishing a decision-making process and governance framework for your team. Implement a review process where ADRs are discussed before finalization, maintain an index of all decisions organized by domain or date, track status (Proposed, Accepted, Deprecated, Superseded), and use ADRs during onboarding to help new members understand historical context and design rationale.","q":"How to manage ADRs in a team?"},{"a":"architecture-decision-records enables you to manage ADR lifecycles through status tracking. Decisions typically progress from Proposed (under discussion) to Accepted (approved), then may be Deprecated (no longer recommended) or Superseded (replaced by newer decisions). This lifecycle management helps teams understand which decisions remain active, which have evolved, and provides clear documentation of architectural evolution over time.","q":"What is the ADR lifecycle and status tracking?"},{"a":"architecture-decision-records captures historical context and design rationale in your ADR index, allowing new team members to quickly understand why architectural choices were made. Rather than relying on tribal knowledge, onboarding becomes systematic\u2014new developers can review the decision history, understand trade-offs, and grasp the reasoning behind current system design through documented architectural records.","q":"How does architecture-decision-records help onboard new team members?"}],"shadow_tags":["decision-documentation","technical-governance","knowledge-capture","design-rationale","team-alignment","architecture-patterns","decision-lifecycle","audit-trail","process-automation"],"summary_rewrite":"Create and maintain Architecture Decision Records that capture the reasoning behind significant technical choices. This skill provides multiple templates\u2014from standard MADR format to lightweight Y-statements\u2014and guidance on when ADRs matter most, helping teams establish clear decision-making processes and onboard members through documented architectural history."},"files":[{"bytes":12730,"path":"plugins/documentation-generation/skills/architecture-decision-records/SKILL.md","sha256":"f8928e30d37eb7654e18adc93c752b43e7272f88054fba5a7813b434779c50e6","url":"https://skillfed.io/files/wshobson/agents/architecture-decision-records/7f32e870/SKILL.md"}],"id":"wshobson/agents/architecture-decision-records","links":{"html":"https://skillfed.io/wshobson/agents/architecture-decision-records","md":"https://skillfed.io/wshobson/agents/architecture-decision-records.md","repo":"https://github.com/wshobson/agents"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":4097,"language":"Python","last_updated":"2026-07-22","license":"MIT","name":"architecture-decision-records","publisher":"wshobson","stars":38308},"relations":{"categories":["architecture","documentation","team-process"],"similar":[{"id":"addyosmani/agent-skills/documentation-and-adrs"},{"id":"shashankswe2020-ux/whoop-mcp/documentation-and-adrs"},{"id":"ancoleman/ai-design-components/generating-documentation"},{"id":"yonatangross/orchestkit/architecture-decision-record"},{"id":"lyndonkl/claude/adr-architecture"},{"id":"spencerpauly/awesome-cursor-skills/architecture-decision-records"},{"id":"tech-leads-club/agent-skills/create-adr"},{"id":"existential-birds/beagle/write-adr"},{"id":"nWave-ai/nWave/nw-database-technology-selection"},{"id":"Jeffallan/claude-skills/architecture-designer"}]},"slug":{"owner":"wshobson","repo":"agents","skill":"architecture-decision-records"},"version":"7f32e870"}