skills.rest
MSiccDev
MSiccDevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

arc42-section-09

Generate ADR documents with context, alternatives, consequences, and decision logs.

20|3|Updated Nov 9, 2025
Search Tags:#architecture#documentation#adr#software-engineering#architecture-decisions#arc42
One-click install
npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-09
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arc42-section-09
Source: https://github.com/MSiccDev/arc42-toolkit/tree/main/skills/arc42-section-09
Command: npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-09

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams systematically capture architecturally significant decisions using ADRs, including rationale, alternatives, and consequences, ensuring traceability over time.

Core Features & Use Cases

  • Guided ADR creation: Walks you through identifying decisions, documenting rationale, and generating structured ADRs.
  • Rationale and alternatives: Captures context, explored options, and trade-offs for future reference.
  • Lifecycle and governance: Enforces ADR lifecycle rules (status, dates, supersession) and keeps a decision log.

Quick Start

Provide the decision context and constraints, and I will generate a complete ADR set.

Frequently Asked Questions about arc42-section-09

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

FAQPage Schema
How do I document architecture decisions for arc42 Section 9?▼

Architecture Decision Records capture architecturally significant decisions, rationale, and trade-offs. They ensure traceability over time by documenting context, alternatives, and consequences within arc42 Section 9.

What is the best way to maintain an architecture decision log?▼

Maintaining an architecture decision log requires enforcing ADR lifecycle rules for status, dates, and supersession. This Skill generates a maintained log that tracks decision governance and traceability over time.

How do I capture rationale and alternatives in software architecture documentation?▼

Capturing rationale and alternatives in architecture documentation involves recording decision context, explored options, and trade-offs. This Skill generates ADRs that systematically document these elements for future reference and traceability.

Can I track architecturally significant decisions with stakeholders and dates?▼

Tracking architecturally significant decisions with stakeholders and dates is supported through generated ADR documents. These documents include stakeholder information, dates, and lifecycle status for governance and traceability.

Does this ADR documentation approach require any specific dependencies?▼

This ADR documentation approach requires no specific dependencies. It independently guides architecture teams through identifying decisions and generating structured ADRs with lifecycle management for arc42 Section 9.

Related Skills

Explore More Software Engineering Skills→
jtvarisjtvaris

architecture-decision

Generate Architecture Decision Records with context, constraints, and alternatives.

Community
Intermediate
silvarojasdiegoarturo91silvarojasdiegoarturo91

ADR Format

Create Architecture Decision Records using prescribed templates and numbering conventions.

Community
Basic
Obsidian-OwlObsidian-Owl
1

arc42-epic-decomposer

Generate a structured Epic catalogue from Arc42 architecture documentation.

Official
Advanced
ekremmkasapekremmkasap

architecture-decision-records

Document architecture decisions with standardized ADR templates and lifecycle tracking.

Community
Advanced