arch

Designs system architecture and documents technical decisions as ADRs from requirements.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill arch-alessioroberto82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch
Source: https://github.com/alessioroberto82/claude-plugin-circle/tree/main/plugins/circle/skills/arch
Command: npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill arch-alessioroberto82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning requirements into a sound technical design is hard: trade-offs go undocumented, project coding standards get ignored, and architecture drifts from what was actually requested. This Skill acts as an Architecture Owner that reads prior requirements, evaluates alternatives, and produces a structured architecture document with ADRs. ## Core Features & Use Cases - Architecture Document Generation: Produces system overviews, component diagrams in Mermaid, data models, API contracts, and concurrency strategies tailored to software, business, or personal domains. - ADR Documentation: Records each significant decision with context, alternatives considered, and consequences in a standard ADR format. - Standards Compliance Verification: Reads project standards (AGENTS.md, CLAUDE.md, .claude/rules/) and appends a per-rule compliance section to the design before handoff. - Use Case: After gathering requirements for a new feature, run this Skill to receive an architecture.md with evaluated technology options, ADRs, and a verified compliance checklist ready for security review and implementation. ## Quick Start Ask the assistant to design the architecture for the feature described in the requirements produced by the scope step.

Frequently Asked Questions about arch

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

FAQPage Schema
How do I generate an architecture document from requirements?▼

Run this Skill after requirements exist in the project output folder. It reads scope/requirements.md or refine/PRD.md, evaluates alternatives, and writes an architecture.md with component diagrams, ADRs, and a data model.

What is an ADR and how does this Skill create one?▼

An ADR (Architecture Decision Record) documents a technical decision with its context, alternatives considered, and consequences. The Skill generates one ADR per significant decision, listing 2-3 options with pros and cons for each.

Does the architecture design follow my project's coding standards?▼

Yes. The Skill runs a mandatory standards baseline step that reads AGENTS.md, CLAUDE.md, and rules under .agents/ and .claude/rules/, then appends a Standards Compliance section marking each applicable rule as compliant, partial, or violated.

What happens if requirements are missing when I run the architecture step?▼

The Skill stops and reports that requirements are missing, directing you to run the scope role first. It can also consume a handoff digest instead of the full requirements document when digest mode is enabled in the project config.

Can this Skill design non-software systems?▼

Yes. It detects the project domain and adapts: business projects get operational architecture with process flows and organizational structure, while personal projects get habit architecture and environment design documents.