architecture

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

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/2good4me/JobNow --skill architecture-2good4me
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/2good4me/JobNow/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/2good4me/JobNow --skill architecture-2good4me

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a framework for making sound architectural decisions, ensuring that system designs are scalable, maintainable, and aligned with project requirements and constraints.

Core Features & Use Cases

  • Requirements Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Facilitates the comparison of different architectural options and their implications.
  • ADR Documentation: Helps in documenting significant architectural decisions using the Architecture Decision Record (ADR) format.
  • Pattern Selection: Offers guidance on choosing appropriate architectural patterns based on project characteristics.
  • Use Case: When starting a new project, use this Skill to analyze requirements, evaluate options like microservices vs. monolith, and document the final decision in an ADR.

Quick Start

Use the architecture skill to analyze requirements for a new SaaS product.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I evaluate architectural trade-offs when choosing between a microservices or monolith design?

Evaluating architectural trade-offs involves comparing options like microservices versus monolith by analyzing project scale, team, timeline, and constraints. This comparison ensures the selected system design aligns with specific domain requirements.

What is an Architecture Decision Record and when should I document one?

An Architecture Decision Record (ADR) documents significant architectural decisions and their context. You should generate an ADR when finalizing a system design to capture requirements analysis, trade-off evaluation, and pattern selection for future reference.

How do I select the right architectural patterns for a new software project?

Selecting the right architectural patterns requires analyzing project characteristics such as scale, team size, timeline, and domain constraints. Using context discovery and example-based references guides the pattern selection process for robust system design.

Can I use this architectural decision-making framework for a small team and tight timeline?

Yes, this architectural decision-making framework explicitly supports pattern selection based on project scale, team composition, and timeline constraints. It adapts to small teams by focusing requirements analysis on specific domain limitations.

What is the best way to document system design decisions for a SaaS product?

The best way to document system design decisions is using the Architecture Decision Record format. This process captures the requirements analysis and trade-off evaluation, ensuring the SaaS architecture remains scalable and maintainable.