skills.rest
pkuppens
pkuppensCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decisions

Capture architectural decisions with context, options, and consequences into arc42-compatible ADRs.

Updated Jan 5, 2025
Search Tags:#architecture#documentation#adr#traceability#arc42#decision-record#adr-generation
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill architecture-decisions-pkuppens
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decisions
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/architecture/architecture-decisions
Command: npx skills add https://github.com/pkuppens/pkuppens --skill architecture-decisions-pkuppens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions can drift over time, leading to inconsistent implementations and lost rationale. This skill ensures decisions are captured, justified, and traceable following arc42 §9 ADR guidelines.

Core Features & Use Cases

  • Create, review, and update Architecture Decision Records (ADRs) aligned with arc42.
  • Maintain a centralized ADR index (e.g., 09-decisions.md) and reference ADRs in design/implementation work.
  • Generate consistent ADR documents to support governance, audits, and onboarding.

Quick Start

Create a new ADR using the standard template, save it under docs/architecture/adr/, and update the ADR index.

Frequently Asked Questions about architecture-decisions

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

FAQPage Schema
How do I create Architecture Decision Records that follow arc42 guidelines?▼

Architecture Decision Records aligned with arc42 §9 are generated using a standard template capturing context, options, and consequences, then saved under docs/architecture/adr/ to ensure decisions remain justified and traceable.

Why do architecture decisions drift over time and how can I maintain traceability?▼

Architecture decisions drift when rationale is lost, but traceability is maintained by updating a centralized ADR index like 09-decisions.md and referencing ADRs in design and implementation work.

What's the best way to document architectural decisions before major implementations?▼

Documenting architectural decisions before major implementations requires generating arc42-compatible ADR documents that capture context, options, and consequences to prevent inconsistent implementations.

Can I use this approach for evolving architectures or only for new projects?▼

Architecture Decision Records apply to evolving architectures as well as new projects, allowing teams to create, review, and update decisions while maintaining a centralized index for governance and onboarding.

How do I maintain an ADR index when new architecture decisions are made?▼

An ADR index is maintained by updating 09-decisions.md each time a new Architecture Decision Record is created under docs/architecture/adr/, ensuring all decisions remain centralized and traceable.

Does this ADR generation approach require any specific dependencies or frameworks?▼

ADR generation following arc42 guidelines requires no external dependencies, producing standard markdown documents under docs/architecture/adr/ and updating the decisions index without additional tooling.

Related Skills

Explore More Software Engineering Skills→
levnikolaevichlevnikolaevich
534

ln-112-project-core-creator

Create requirements, architecture, and tech stack documentation files for any project.

Community
Advanced
scanadyscanady

tech-arch-architecture-decision-records

Create and index Architecture Decision Records using MADR and other templates.

Community
Advanced
MSiccDevMSiccDev
20

arc42-lint

Detect cross-section ID inconsistencies in arc42 documentation.

Official
Advanced
dralgorhythmdralgorhythm
111

writing-adrs

Document architectural decisions using ADR format with Title, Status, Context, Decision, Rationale, and Consequences.

Community
Advanced