architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions with ADRs.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Ab-aswini/Agent-kit-P1 --skill architecture-ab-aswini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Ab-aswini/Agent-kit-P1/tree/main/.agent-os/skills/architecture
Command: npx skills add https://github.com/Ab-aswini/Agent-kit-P1 --skill architecture-ab-aswini

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 requirements are met, trade-offs are evaluated, and rationale is documented through 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 different architectural options.
  • ADR Documentation: Facilitates the creation and management of Architecture Decision Records.
  • Use Case: When starting a new project, use this Skill to systematically analyze requirements, explore design patterns, document the chosen architecture, and ensure all critical decisions are captured for future reference.

Quick Start

Use the architecture skill to document a new decision about choosing a database for a new project.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architectural decisions for a new software project?

You can document architectural decisions using the Architecture Decision Record (ADR) templates provided by this Skill. It helps you capture requirements, evaluate trade-offs, and record the rationale for your system design choices to ensure justifiable architectural outcomes.

What is the best way to evaluate trade-offs in system design?

Evaluating trade-offs in system design requires a structured framework for analyzing different architectural options against project constraints. This Skill provides methods and templates to systematically compare design patterns and document the resulting architectural choices.

How do I use design patterns to guide architectural decision making?

To guide architectural decision making with design patterns, this Skill offers pattern selection guidelines and decision trees. These tools help you systematically match your requirements analysis against established patterns to make informed design choices.

When do I need to create an Architecture Decision Record?

You need to create an Architecture Decision Record when starting a new project or making significant system design changes that require documented rationale. This ensures that critical architectural choices, trade-offs, and constraints are captured for future reference.

Can I use this architectural framework for any software system design?

Yes, this architectural framework supports systematic design choices for general software systems. It provides decision trees and trade-off evaluation methods that are applicable whenever you need clear, documented, and justifiable architectural choices in software development.

What are the limitations of using a structured framework for architectural decision making?

A structured framework for architectural decision making requires upfront requirements analysis and manual trade-off evaluation. While it provides ADR templates and decision trees, the quality of the architectural choices still depends entirely on the accuracy of your input requirements.