software-architect

Analyze codebases with a six-layer framework for structure, patterns, and modernization.

1|1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/PearlThoughts/CodeCompass --skill software-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/PearlThoughts/CodeCompass/tree/main/.claude/skills/software-architect
Command: npx skills add https://github.com/PearlThoughts/CodeCompass --skill software-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding complex legacy system architectures, planning migrations, and assessing technical debt manually is a daunting, time-consuming, and error-prone task. This Skill provides a structured framework to automate architectural analysis.

Core Features & Use Cases

  • 6-Layer Architectural Framework: Analyzes system structure, domain model, design patterns, technical debt, modernization strategy, and Domain-Driven Design (DDD) aspects.
  • Technical Debt Assessment: Categorizes and quantifies code, architectural, infrastructure, and documentation debt, prioritizing fixes.
  • Modernization Strategy: Guides through common migration patterns like Strangler Fig and Branch by Abstraction, generating a phased roadmap.
  • Use Case: Analyze a legacy PHP application to identify its core domain entities, assess technical debt, and generate a step-by-step roadmap for migrating to a modern microservices architecture.

Quick Start

Use the software-architect skill to analyze the attached codebase and provide a technical debt assessment and a modernization strategy.

Frequently Asked Questions about software-architect

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

FAQPage Schema
How do I assess technical debt in a legacy codebase?

Technical debt assessment categorizes and quantifies code, architectural, infrastructure, and documentation debt across your system. This Skill analyzes these layers and prioritizes fixes, helping you understand what accumulated problems exist and where to focus remediation efforts.

What's the best way to plan a migration from a legacy system to microservices?

Modernization strategy guides you through migration patterns like Strangler Fig and Branch by Abstraction, generating a phased roadmap. The Skill delivers step-by-step planning tailored to your architecture, reducing migration risk and complexity.

How do I identify design patterns and structure in an existing codebase?

Architectural analysis reveals system structure, domain model, and design patterns through a six-layer framework. You get Mermaid diagrams, pattern catalogs, and documentation that expose your codebase's organization and architectural decisions.

Can I use Domain-Driven Design analysis to understand my system architecture?

Yes. DDD analysis is one of the six layers in the architectural framework, helping you map domain entities, bounded contexts, and business logic. This clarifies how your domain model aligns with your code structure.

What outputs do I get from a complete architectural analysis?

A complete analysis delivers Mermaid diagrams for visualization, domain models, pattern catalogs, technical debt reports with prioritized fixes, modernization roadmaps, and architecture documentation—everything needed to act on findings.

Is architectural analysis applicable to systems I'm planning to refactor?

Yes. The Skill is built for legacy systems modernization, migration planning, debt assessment, and refactoring scenarios. It identifies what needs to change and how to sequence those changes systematically.