skills.rest
Harmitx7
Harmitx7COMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture

Analyze requirements, evaluate trade-offs, and document Architecture Decision Records.

3|1|Updated Feb 20, 2026
Search Tags:#architecture#decision making#documentation#system design#ADR#trade-offs
One-click install
npx skills add https://github.com/Harmitx7/tribunal-kit --skill architecture-harmitx7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Harmitx7/tribunal-kit/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/Harmitx7/tribunal-kit --skill architecture-harmitx7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides a structured framework for making and documenting critical architectural decisions, ensuring clarity, alignment, and maintainability in system design.

Core Features & Use Cases

  • Requirements Analysis: Helps map out system constraints and quality attributes.
  • Option Generation & Evaluation: Facilitates the creation and comparison of multiple design alternatives.
  • ADR Documentation: Guides the creation of Architecture Decision Records to capture the "why" behind choices.
  • Use Case: When deciding between a monolith and microservices for a new project, use this Skill to analyze trade-offs based on team size, scaling needs, and development speed, and document the final decision.

Quick Start

Use the architecture skill to help document a new system design decision.

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 and evaluate trade-offs for system design?▼

An Architecture Decision Record (ADR) is a document that captures the context, options, and trade-offs evaluated during system design to explain why a specific architectural decision was made for future maintainability.

What is the best way to analyze requirements and constraints before modifying a system architecture?▼

Analyzing requirements involves mapping out system constraints and quality attributes to ensure the architecture aligns with team size, scaling needs, and development speed before evaluating structural design modifications.

Can I use this framework to decide between a monolith and microservices architecture?▼

Yes, you can use the framework to compare monolith and microservices architectures by analyzing trade-offs based on your team size, scaling requirements, and development speed, then documenting the final decision.

When do I need to write an Architecture Decision Record for a software project?▼

You need to write an Architecture Decision Record when making critical architectural choices for a new system or significant modification, ensuring structured design processes, clarity, and alignment across the team.

Related Skills

Explore More Software Engineering Skills→
aget-frameworkaget-framework
11

aget-assess-tradeoffs

Evaluate architectural options against quality attributes and reversibility.

Official
Intermediate
kartikkabadikartikkabadi

grill-with-docs

Challenge proposed plans against codebase language and documented decisions.

Community
Intermediate
brenordvbrenordv

system-architect

Generate architectural plans, ADRs, and C4 model diagrams in Mermaid syntax.

Community
Advanced
alex-tgkalex-tgk

senior-architect

Generate architecture diagrams and analyze project dependencies for software systems.

Community
Intermediate