architecture

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

Updated Aug 5, 2025
One-click install
npx skills add https://github.com/lehuuhau1231/TechJobs --skill architecture-lehuuhau1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/lehuuhau1231/TechJobs/tree/main/tech-job-client/.agent/skills/architecture
Command: npx skills add https://github.com/lehuuhau1231/TechJobs --skill architecture-lehuuhau1231

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured approach to architectural decision-making, helping you analyze requirements, evaluate trade-offs, and document decisions effectively.

Core Features & Use Cases

  • Requirements Analysis: Offers guidelines for understanding project context and constraints.
  • Trade-off Evaluation: Assists in making well-informed decisions through a trade-off analysis framework.
  • ADR Documentation: Provides templates and best practices for documenting architectural decisions.
  • Use Case: Ideal for software architects or project leads involved in designing complex systems, ensuring that all decisions are well-documented and justified.

Quick Start

Use the architecture skill to generate an ADR for a new feature in your 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 a new software feature?

Document architectural decisions by using a structured framework to guide requirements analysis, evaluate trade-offs, and generate ADR documentation. This ensures all system design choices are well-justified and recorded for future reference.

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

Evaluate trade-offs in system design by applying a structured analysis framework that compares architectural patterns against project constraints. This approach helps software architects make well-informed decisions for complex systems.

When do I need to write an ADR for my software architecture?

Write an ADR when you need to document significant architectural decisions and their driving factors during system analysis. It is ideal for project leads designing complex systems who need to justify and record trade-off evaluations.

How do I analyze project requirements before making architectural decisions?

Analyze project requirements by following guidelines that help you understand the project context and technical constraints. This structured requirements analysis forms the foundation for effective architectural decision-making.

Do I need prior knowledge of architectural patterns to use this decision-making framework?

Yes, understanding architectural patterns and decision-making frameworks is required. The framework assists in the decision process but expects users to have a foundational grasp of software architecture design to evaluate trade-offs effectively.

Can this framework help with system analysis beyond software architecture design?

Yes, the framework is applicable to both software architecture design and broader system analysis processes. It provides a structured approach to decision-making that extends to evaluating requirements and documenting outcomes in complex environments.