assessing-architecture-quality

Assess codebase architecture quality with evidence and severity ratings.

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/tachyon-beep/hamlet --skill assessing-architecture-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assessing-architecture-quality
Source: https://github.com/tachyon-beep/hamlet/tree/main/.claude/skills/axiom-system-architect/skills/assessing-architecture-quality
Command: npx skills add https://github.com/tachyon-beep/hamlet --skill assessing-architecture-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps practitioners produce accurate, evidence-based assessments of software architecture despite conflicting stakeholder pressures, ensuring decisions are based on reality.

Core Features & Use Cases

  • Direct assessment statements: State the architecture quality level with explicit evidence and severity.
  • Evidence-based critique: Provide concrete examples and file references to justify findings.
  • Operational templates: Produce structured reports for stakeholders and decision-makers.
  • Use Case: Create architecture quality assessments for client projects, internal refactors, or architecture review sessions.

Quick Start

Provide an objective architecture assessment by following the standard structure: Assessment Summary, Evidence, Architectural Problems, Impact Analysis, and Recommendations. Include concrete file references as evidence and assign a severity rating.

Frequently Asked Questions about assessing-architecture-quality

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

FAQPage Schema
How do I assess software architecture quality with evidence?

Generate architecture review reports by structuring findings into Assessment Summary, Evidence, Architectural Problems, Impact Analysis, and Recommendations sections. Include concrete file references and assign severity ratings to each identified issue.

What is evidence-based architecture critique?

Evidence-based architecture critique evaluates codebase designs by providing direct assessment statements backed by concrete file references. It replaces subjective opinions with objective severity ratings and explicit operational evidence.

Can I use a structured assessment for internal refactors and client projects?

Structured architecture assessments apply directly to internal refactors, client project evaluations, and architecture review sessions. They scale effectively across projects of varying size and complexity for stakeholder-facing reporting.

What's the best way to assign severity ratings during a codebase evaluation?

Assign severity ratings by categorizing architectural problems into Critical, High, Medium, or Low levels. Back each rating with concrete file references and evidence to justify the assigned severity for decision-makers.

Why do I need explicit file references in an architecture review report?

Explicit file references are required in architecture review reports to provide concrete evidence justifying direct assessment statements. This ensures stakeholder-facing reports remain objective and grounded in actual codebase reality.