arch-design

Generate ARCH.md overviews and ADR-NNN.md files from confirmed SPEC.md requirements.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill arch-design-anjinmeili
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-design
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/arch-design
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill arch-design-anjinmeili

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ARCH.md overviews and ADR documents to capture and communicate architectural decisions, ensuring traceability from requirements to implementation.

Core Features & Use Cases

  • Generates ARCH.md as the living system overview, describing the system context, component responsibilities, data model, interface contracts, and deployment model.
  • Produces ADR-NNN.md files for significant architectural decisions, including rationale, consequences, and rejected alternatives.
  • Enables an auditable artifact chain that supports governance, reviews, and future references during evolution.

Quick Start

Invoke arch-design after SPEC.md is confirmed to generate ARCH.md and ADR-NNN.md files

Frequently Asked Questions about arch-design

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

FAQPage Schema
How do I document system architecture decisions for traceability and governance?

Generate ARCH.md and ADR-NNN.md files to capture architectural boundaries, component responsibilities, and rationales. This creates a repeatable, auditable artifact chain linking requirements to implementation for governance.

What is an ARCH.md file and when do I need to create it?

ARCH.md is a living system overview describing system context, component responsibilities, data models, interface contracts, and deployment models. Create it after SPEC.md is confirmed and requirements are stable to translate them into architectural boundaries.

What should an Architecture Decision Record include for rejected alternatives?

An ADR-NNN.md file should include rationale, consequences, and rejected alternatives for significant decisions. This records context for future references during system evolution and supports governance reviews.

How do I translate confirmed requirements into interface contracts and deployment models?

Translate confirmed requirements into interface contracts and deployment models by invoking architecture generation after SPEC.md is confirmed. This produces ARCH.md overviews and ADR documents defining component interactions and deployment architecture.

Do I need a confirmed SPEC.md before generating architecture overviews?

Yes, a confirmed SPEC.md is required before generating architecture overviews. The process is applied after requirements are stable to translate them into architectural boundaries, components, and data models.