analyzing-architecture

Generate architecture design documents and ADRs from requirements and user stories.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/k2works/claude-code-booster --skill analyzing-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-architecture
Source: https://github.com/k2works/claude-code-booster/tree/main/lib/assets/.claude/skills/analyzing-architecture
Command: npx skills add https://github.com/k2works/claude-code-booster --skill analyzing-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decision support for backend, frontend, and infrastructure by generating architecture design documents and ADRs.

Core Features & Use Cases

  • Architecture pattern selection (layered, hexagonal, clean, etc.) and documentation for backend, frontend, and infrastructure.
  • ADR generation and design doc artifacts aligned to requirements, use cases, and user stories.
  • Use Case: Given requirements, this skill proposes architecture options and produces design docs ready for ADR entries.

Quick Start

Provide project requirements and user stories to generate architecture design documents covering backend, frontend, and infrastructure.

Frequently Asked Questions about analyzing-architecture

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

FAQPage Schema
How do I generate architecture design documents from requirements and user stories?

Architecture design documents are generated by providing project requirements and user stories to produce ADR-based artifacts covering backend, frontend, and infrastructure decisions with multiple pattern options.

What is the best way to choose between layered, hexagonal, and clean architecture patterns for my project?

Choosing between layered, hexagonal, and clean architecture patterns involves evaluating defined requirements, system use cases, and user stories to propose matching options and document the selection rationale in ADR entries.

Can I create ADRs for backend, frontend, and infrastructure architecture decisions together?

ADRs for backend, frontend, and infrastructure architecture decisions are created together by processing project requirements to produce unified architecture design documents with pattern selection and documented rationale.

How does architecture decision support work for multi-layer system design?

Architecture decision support for multi-layer design works by taking defined requirements and user stories to propose architecture options, select patterns, and generate design documents ready for ADR entries.

Do I need defined system use cases before generating architecture documentation?

Defined system use cases are required before generating architecture documentation because the output design documents and ADR entries are aligned directly to those use cases and user stories.

What limitations exist when proposing infrastructure architecture patterns from user stories?

Limitations when proposing infrastructure architecture patterns include the dependency on fully defined requirements and user stories, as the generated design documents and ADRs are strictly aligned to the provided inputs without inferring missing context.