architecture

Coordinate architecture decisions by analyzing requirements and documenting ADRs.

2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ivanshtokov/copilot-kit --skill architecture-ivanshtokov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ivanshtokov/copilot-kit/tree/main/.github/skills/architecture
Command: npx skills add https://github.com/ivanshtokov/copilot-kit --skill architecture-ivanshtokov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision making can be chaotic without a repeatable process. This framework guides teams through requirements analysis, alternative exploration, and ADR-based documentation to ensure clear, traceable decisions.

Core Features & Use Cases

  • Context discovery prompts to elicit project constraints and goals.

  • ADR templates and example patterns to document decisions with rationale.

  • Pattern references and trade-off checklists to compare options across teams.

  • Use cases: evaluating a new tech stack, choosing between modular monolith vs microservices, and capturing decisions for audits or onboarding.

Quick Start

Provide an ADR-style architecture decision for a project by outlining context, options, and recommended decision.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architecture decisions and evaluate trade-offs for a new system design?

Architecture decision records provide a structured format to capture context, evaluated options, and recommended decisions, ensuring traceability and clear communication for audits, onboarding, and team alignment.

What is the best way to choose between a modular monolith and microservices architecture?

Choosing between a modular monolith and microservices requires evaluating trade-offs using pattern references and checklists to compare options against your specific project constraints, goals, and scale requirements.

How do I write an ADR for evaluating a new technology stack?

To write an ADR for a new technology stack, outline the project context, list alternative options, evaluate trade-offs, and state the recommended decision using provided templates to ensure consistent documentation.

Can I use this architecture decision framework for small applications or is it only for large systems?

You can use this architecture decision framework for projects of varying sizes, from small applications to large systems, ensuring clear architectural decisions and maintained ADRs across different scales.

Why does my team need a structured framework for system design decision-making?

A structured framework for system design decision-making prevents chaotic architectural choices by providing a repeatable process for requirements analysis, alternative exploration, and ADR-based documentation.