assess-architecture

Assess architecture patterns and record the decision as an ADR.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill assess-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assess-architecture
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/capability/assess-architecture
Command: npx skills add https://github.com/foomakers/pair --skill assess-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires /record-decision, and includes references (resource) components.

What problem does it solve?

This Skill helps developers and teams select and adopt the most suitable architecture pattern for their project, ensuring alignment with project constraints and best practices.

Core Features & Use Cases

  • Automated Assessment: Evaluates architecture patterns based on project context and guidelines.
  • Resolution Cascade: Prioritizes explicit arguments, then existing adoption, before performing a full assessment.
  • Decision Recording: Automatically creates an Architecture Decision Record (ADR) for adopted patterns.
  • Use Case: When starting a new project or refactoring an existing one, this Skill guides the team through choosing between patterns like Hexagonal, Microservices, or Modular Monolith, documenting the decision formally.

Quick Start

Use the assess-architecture skill to evaluate and choose an architecture pattern for the new project.

Frequently Asked Questions about assess-architecture

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

FAQPage Schema
How do I choose the right architecture pattern for a new software project?

To choose an architecture pattern, you must evaluate project constraints and guidelines against options like Hexagonal or Microservices. This assessment uses a resolution cascade of explicit arguments and existing adoption to select the optimal pattern.

How do I document architectural decisions when adopting a new system design?

Document architectural decisions by generating an Architecture Decision Record (ADR). The assessment process automatically records the final system design choice as an ADR, ensuring formal documentation and adherence to project guidelines.

What is the best way to evaluate Microservices versus a Modular Monolith for an application?

Evaluating Microservices versus a Modular Monolith requires a guideline-based assessment of your project context. A resolution cascade prioritizes explicit arguments and existing adoption to recommend the correct system design.

Can I assess existing architecture adoption before deciding on a new design pattern?

Yes, you can assess existing architecture adoption before deciding on a new design pattern. The evaluation cascade explicitly checks existing adoption levels before performing a full guideline-based assessment.

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

You need an Architecture Decision Record (ADR) when finalizing any system design choice. Recording architectural decisions in an ADR ensures consistency, formalizes the adoption of patterns like Hexagonal, and verifies adherence to constraints.

Does the architecture assessment process support the Hexagonal pattern?

Yes, the architecture assessment process supports the Hexagonal pattern. It evaluates various architecture patterns, including Hexagonal and Microservices, against project guidelines to determine the best fit.