skills.rest
jabez4jc
jabez4jcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture

Analyze requirements, evaluate trade-offs, and document architecture decisions in ADRs.

Updated Nov 12, 2025
Search Tags:#architecture#decision making#documentation#design patterns#adr#trade-offs
One-click install
npx skills add https://github.com/jabez4jc/Simplifyed --skill architecture-jabez4jc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/jabez4jc/Simplifyed/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/jabez4jc/Simplifyed --skill architecture-jabez4jc

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 system designs are well-reasoned, documented, and aligned with project requirements and constraints.

Core Features & Use Cases

  • Requirements Analysis: Guides the process of gathering essential project context (scale, team, timeline, domain, constraints).
  • Trade-off Evaluation: Provides templates and guidance for analyzing the pros and cons of different architectural options.
  • ADR Documentation: Facilitates the creation of Architecture Decision Records to capture rationale and history.
  • Pattern Selection: Offers decision trees and references for choosing appropriate design patterns.
  • Use Case: When starting a new project, use this Skill to systematically gather requirements, evaluate database choices (e.g., SQL vs. NoSQL), and document the decision in an ADR.

Quick Start

Use the architecture skill to help 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 choosing between SQL and NoSQL databases?▼

Architecture Decision Records (ADRs) document architectural decisions by capturing requirements, trade-off evaluations, and rationale for choices like SQL versus NoSQL databases. This framework provides templates to systematically structure and record decision history.

What is the best way to evaluate architectural trade-offs when designing a new system?▼

Evaluating architectural trade-offs requires analyzing project constraints like scale, team, and timeline against different design patterns. This framework guides you through systematically comparing the pros and cons of various options to ensure well-reasoned system design choices.

When do I need to create an Architecture Decision Record for my software project?▼

You need to create an Architecture Decision Record when making significant system design choices that require documented rationale, such as selecting foundational design patterns or database technologies. It addresses the need for structured, rational, and documented architectural choices in software engineering.

How do I select appropriate design patterns based on specific project requirements?▼

Selecting appropriate design patterns involves using decision trees to match your specific project requirements and constraints against available options. This framework offers references to guide pattern selection while adhering to core principles like simplicity.

Can I use this framework to gather requirements before making system design choices?▼

Yes, you can use this framework to gather requirements by analyzing essential project context including scale, team, timeline, domain, and constraints. This requirements analysis forms the foundational step before evaluating architectural options and documenting decisions.

Related Skills

Explore More Software Engineering Skills→
2good4me2good4me

architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions in ADR format.

Community
Advanced
yunaameliayunaamelia

architecture

Guide architectural decisions through requirements analysis, trade-off evaluation, and ADR documentation.

Community
Intermediate
miethemiethe

planning

Generate PRDs and phased implementation plans with subagent assignments.

Community
Advanced
ammonfifeammonfife

self-review

Review past agent turns against violation patterns and todo management protocols.

Community
Advanced