skills.rest
ChrstprJohn
ChrstprJohnCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Record architectural decisions with ADR templates and trade-off evaluation.

6|Updated Mar 1, 2026
Search Tags:#architecture#documentation#adr#trade-offs#decision-making#architecture-decisions#requirements-analysis
One-click install
npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill architecture-chrstprjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ChrstprJohn/SamsonDentalCenter/tree/main/.agent/skills/SystemArchitecture/architecture
Command: npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill architecture-chrstprjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision fatigue is common when teams must weigh requirements, trade-offs, and rationale. This framework provides structure to capture context, options, and ADRs to guide design decisions.

Core Features & Use Cases

  • ADR documentation templates to capture decisions and rationale
  • Requirements analysis and constraint capture for architecture initiatives
  • Trade-off evaluation guidance and repeatable decision workflows
  • Use Case: when comparing multiple architectural approaches, record alternatives and rationale for future traceability

Quick Start

Describe the current architecture goal, gather constraints, and record the ADRs using the framework.

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 trade-offs to reduce decision fatigue?▼

Architectural decision records document context, evaluated options, and rationale. This framework provides structured ADR templates to capture alternatives and justification, reducing decision fatigue by creating traceable architecture decisions.

What is an ADR and when do I need to write one for my architecture?▼

An ADR, or Architecture Decision Record, captures context, options, and rationale for design choices. You need ADRs when comparing multiple architectural approaches to ensure future rationale traceability against project constraints.

How do I evaluate architecture trade-offs and compare multiple design options?▼

You evaluate architecture trade-offs by performing requirements analysis and applying repeatable decision workflows. This framework guides end-to-end option comparison, weighing constraints against alternatives to clarify the most suitable architectural approach.

Can I use this architecture framework for both MVP and enterprise projects?▼

Yes, you can scope requirements analysis, trade-off evaluation, and ADR documentation across projects from MVPs to enterprise. The framework satisfies end-to-end requirements capture and option comparison at any architectural scale.

What is the best way to start capturing requirements and constraints for a new architecture initiative?▼

The best way to start is to describe your current architecture goal and gather constraints. The framework provides structured templates to capture context, perform requirements analysis, and record linked ADR artifacts for the initiative.

Related Skills

Explore More Software Engineering Skills→
OmarMiraOmarMira

architecture

Guide architectural decision-making with requirements analysis and ADR documentation.

Community
Intermediate
CygnusfearCygnusfear
5

the-archivist

Document engineering decisions as ADRs with rationale and decision logs.

Community
Advanced
0xRayAI0xRayAI

architect-tools

Provides tools for system design, architecture planning, and decision documentation.

Official
Intermediate
cyhinversecyhinverse

architecture

Capture and justify architectural decisions using ADR templates and decision records.

Community
Advanced