architecture

Facilitate architectural decisions with ADR documentation and trade-off analysis.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/ofelixdev/cc-kit --skill architecture-ofelixdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ofelixdev/cc-kit/tree/main/template/skills/architecture
Command: npx skills add https://github.com/ofelixdev/cc-kit --skill architecture-ofelixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, ensuring that requirements are met, trade-offs are evaluated, and decisions are well-documented through Architecture Decision Records (ADRs).

Core Features & Use Cases

  • Requirements Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Offers methods and templates for analyzing the pros and cons of different architectural choices.
  • ADR Documentation: Facilitates the creation of clear, concise ADRs to capture the rationale behind decisions.
  • Use Case: When designing a new microservice, use this Skill to systematically explore options like REST vs. gRPC, choose the most suitable database, and document the decision with a clear ADR.

Quick Start

Use the architecture skill to document a new decision for a scalable web application.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document trade-offs for system design choices using ADRs?

Document architectural trade-offs by evaluating requirements and constraints, then capturing the rationale in an Architecture Decision Record. This framework uses structured markdown templates to guide requirements analysis and systematic documentation of software design choices.

What is the best way to evaluate architectural trade-offs for a new microservice?

Evaluating architectural trade-offs requires analyzing project needs against different design choices. This decision-making framework offers structured methods and decision trees to compare options like REST versus gRPC, ensuring the selected architecture meets system requirements.

How does an architectural decision-making framework handle requirements analysis?

An architectural decision-making framework handles requirements analysis by guiding the process of understanding project needs and constraints. It utilizes structured templates to ensure all system design requirements are systematically evaluated before making an architectural choice.

Can I use markdown templates to create Architecture Decision Records for software systems?

Yes, you can use markdown templates to create Architecture Decision Records. The framework provides structured markdown templates and decision trees to facilitate clear, concise documentation of the rationale behind software system design choices.

When do I need an Architecture Decision Record for my software architecture?

You need an Architecture Decision Record when making significant software architecture choices that require documented rationale. The framework captures requirements analysis and trade-off evaluation, ensuring systematic design decisions are recorded for future reference and team alignment.