architecture

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

6|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/paulojalowyj/openkit --skill architecture-paulojalowyj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/paulojalowyj/openkit/tree/main/.opencode/skills/architecture
Command: npx skills add https://github.com/paulojalowyj/openkit --skill architecture-paulojalowyj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making critical architectural decisions, ensuring that designs are well-reasoned, documented, and aligned with project goals and constraints.

Core Features & Use Cases

  • Requirements Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Facilitates the systematic comparison of different architectural options.
  • ADR Documentation: Helps in creating clear and concise Architecture Decision Records.
  • Pattern Selection: Offers decision trees and guidance for choosing appropriate architectural patterns.
  • Use Case: When starting a new project, use this Skill to systematically gather requirements, evaluate options like monolith vs. microservices, and document the final decision in an ADR.

Quick Start

Use the architecture skill to help document the decision for 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 decision making for a new software project?

System design trade-offs are evaluated by systematically comparing architectural options against project requirements and constraints, using a structured framework to validate pattern selection and document the resulting decisions in an ADR.

What is the best way to choose between architectural patterns like monolith vs microservices?

Choosing architectural patterns involves using decision trees and guidance to evaluate trade-offs between options like monolith vs microservices, validating the selection against project constraints, and documenting the final choice in an ADR.

When do I need to write an Architecture Decision Record for system design?

Architectural pattern selection is supported by decision trees and validation checklists that guide the evaluation of trade-offs, ensuring pattern choices are defensible and aligned with system design requirements.

Does this framework require specific dependencies for requirements analysis?

This framework requires no external dependencies to perform requirements analysis, offering a standalone structure for gathering project needs, evaluating system design options, and producing Architecture Decision Records.