skills.rest
DaytimeBlues
DaytimeBluesCOMMUNITY
Explore all skills by this author →
GitHub

architecture

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

Updated Jan 31, 2026
Search Tags:#architecture#decision making#system design#design patterns#ADR#trade-offs
One-click install
npx skills add https://github.com/DaytimeBlues/ADHD-CADDI --skill architecture-daytimeblues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/DaytimeBlues/ADHD-CADDI/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/DaytimeBlues/ADHD-CADDI --skill architecture-daytimeblues

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 Architecture Decision Records (ADRs).

Core Features & Use Cases

  • Requirements Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Offers frameworks and templates for analyzing the pros and cons of different architectural options.
  • ADR Documentation: Facilitates the creation and management of Architecture Decision Records to capture design rationale.
  • Use Case: When starting a new project, use this Skill to systematically define requirements, explore design patterns, and document the chosen architecture using ADRs.

Quick Start

Use the architecture skill to document a new decision using the ADR template.

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 by using an Architecture Decision Record (ADR) template to capture design rationale, evaluate trade-offs, and ensure your system design choices are justifiable and maintainable.

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

Evaluating trade-offs in system design requires a structured framework to analyze the pros and cons of different architectural options, ensuring requirements are met before documenting the final choice in an ADR.

When do I need to use Architecture Decision Records?▼

You need to use Architecture Decision Records (ADRs) when starting a new project or making significant system design changes, ensuring that requirements analysis and the rationale behind design patterns are clearly documented.

How can I systematically select design patterns for my software architecture?▼

Systematically select design patterns by using a framework that offers decision trees and pattern selection guidelines, allowing you to align your choices with specific project requirements and constraints.

Does this architectural decision-making framework work without external dependencies?▼

Yes, this architectural decision-making framework operates with no external dependencies, providing built-in requirements analysis, trade-off evaluation, and ADR templates to support maintainable system designs directly.

Related Skills

Explore More Software Engineering Skills→
alessioroberto82alessioroberto82

scope

Gather requirements and define project scope for new features.

Community
Intermediate
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic
VSF-QC-TTSVSF-QC-TTS

common-architecture-diagramming

Standardize architecture diagrams using C4 and UML models with Mermaid syntax.

Official
Intermediate
nktfh100nktfh100
1

architecture-designer

Design high-level system architectures and ADRs with Mermaid diagrams.

Community
Advanced