architecture

Generate ADRs in MADR format and arc42 documentation.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/salemaziel/digital-innovation-agents --skill architecture-salemaziel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/salemaziel/digital-innovation-agents/tree/main/skills/architecture
Command: npx skills add https://github.com/salemaziel/digital-innovation-agents --skill architecture-salemaziel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill bridges the gap between high-level requirements and detailed architectural plans, enabling efficient design and decision-making processes.

Core Features & Use Cases

  • ADRs Creation: Automates the generation of Architecture Decision Records (ADRs) and arc42 documentation.
  • Plan Context: Provides a compact handoff document (plan-context.md) for seamless integration with Claude Code.
  • Use Case: When architecting a new feature or system, this skill helps you create ADRs and arc42 documentation, ensuring a structured approach to architectural decisions.

Quick Start

Run the architecture skill after completing the requirements phase with the command: 'use architecture'.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I automate Architecture Decision Records creation from software requirements?

Automating Architecture Decision Records (ADRs) creation involves translating high-level software requirements into structured technical design decisions. This Skill generates ADRs in MADR format and produces arc42 documentation to bridge the gap between requirements and architectural blueprints.

What is the best way to document system design decisions using arc42?

Documenting system design decisions using arc42 requires translating requirements into a structured architectural blueprint. This Skill automates arc42 documentation generation, handling ADR abstraction and consolidation to ensure a comprehensive technical design approach.

When do I need to generate MADR format documentation for my tech stack?

You need MADR format documentation during the architectural phase of software development when translating requirements into technical design decisions. It is intended for structuring solution design choices and abstracting, consolidating, and generating architectural decision records.

How do I create a plan-context.md handoff document for Claude Code?

Creating a plan-context.md handoff document for Claude Code is automated by this Skill after completing the requirements phase. It provides a compact handoff document for seamless integration, ensuring architectural decisions are smoothly transitioned into implementation.

Can I use this architecture skill to consolidate multiple ADRs into a single solution design?

Yes, you can use this architecture skill to consolidate multiple ADRs into a single solution design. It handles ADR abstraction and consolidation, automating the generation of comprehensive arc42 documentation and architectural blueprints from your technical decisions.