architecture-eval

Evaluate system architecture using structured quality frameworks.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cjohnhanson/codelikecody --skill architecture-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-eval
Source: https://github.com/cjohnhanson/codelikecody/tree/main/skills/architecture-eval
Command: npx skills add https://github.com/cjohnhanson/codelikecody --skill architecture-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture evaluation provides a structured, repeatable approach to analyzing complex systems for quality, risk, and decision justification.

Core Features & Use Cases

  • Eight-phase evaluation framework including ATAM, ISO 25010, C4 layering, ADR reviews, and Conway's Law alignment.
  • Actionable deliverables: a prioritized findings table, sensitivity/tradeoff mapping, and maintenance guidance.
  • Supports traceability of architectural decisions and architectural debt across teams and time.

Quick Start

Follow the eight-phase framework to assess your architecture and surface actionable improvements.

Frequently Asked Questions about architecture-eval

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

FAQPage Schema
How do I evaluate system architecture for quality attributes and risks?

System architecture evaluation uses a structured eight-phase framework including ATAM and ISO 25010 to analyze complex systems, uncovering tradeoffs, sensitivities, and risks. It provides actionable deliverables like prioritized findings and maintenance guidance.

What is the best way to map architectural tradeoffs using C4 model layering?

Mapping architectural tradeoffs requires applying C4 model layering alongside ATAM within an architecture evaluation framework. This structured approach surfaces sensitivity points and tradeoffs across cloud platforms and enterprise software while ensuring architectural decision traceability.

When do I need ADR traceability for an enterprise software redesign?

ADR traceability is needed during enterprise software redesigns to justify architectural decisions and track architectural debt across teams and time. Architecture evaluation provides structured reviews to ensure decisions align with Conway's Law and quality frameworks.

Can I use ISO 25010 coverage to assess cloud platform architecture?

ISO 25010 coverage can be applied to assess cloud platform architecture by evaluating structured quality attributes within an eight-phase framework. This approach uncovers maintenance risks and provides actionable improvements for complex cloud systems.

Does architecture evaluation work with Conway's Law alignment for team structures?

Architecture evaluation incorporates Conway's Law considerations to align system architecture with team communication structures. The framework evaluates organizational impacts alongside C4 layering and ADR reviews to surface architectural debt and maintenance risks.

What are the limitations of using ATAM for architecture evaluation?

ATAM limitations are mitigated by embedding it within a broader eight-phase architecture evaluation framework that includes ISO 25010 coverage, C4 model layering, and ADR traceability, ensuring comprehensive risk and tradeoff analysis for complex systems.