skills.rest
tachyon-beep
tachyon-beepCOMMUNITY
Explore all skills by this author →
GitHub

using-system-architect

Assess architecture quality and catalog technical debt from archaeologist outputs.

14|3|Updated Oct 28, 2025
Search Tags:#architecture#refactoring#prioritization#technical-debt
One-click install
npx skills add https://github.com/tachyon-beep/skillpacks --skill using-system-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-system-architect
Source: https://github.com/tachyon-beep/skillpacks/tree/main/plugins/axiom-system-architect/skills/using-system-architect
Command: npx skills add https://github.com/tachyon-beep/skillpacks --skill using-system-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This meta-skill routes you to the right architecture-focused skills to critique, prioritize, and improve an existing codebase.

Core Features & Use Cases

  • Direct routing to assessment, debt identification, prioritization, and handover workflows
  • Supports structured decision making for refactoring and improvement planning
  • Guides users toward architect-level outputs and roadmaps

Quick Start

When asked to assess an architecture, say: "What should we fix first in this system?" and the router will guide you to the appropriate architect skill.

Frequently Asked Questions about using-system-architect

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

FAQPage Schema
How do I assess architecture quality and identify what to refactor first?▼

Architecture assessment evaluates your system's design based on subsystem catalogs, diagrams, and reports to surface technical debt, prioritize refactoring opportunities, and create evidence-based improvement roadmaps ranked by risk and impact.

What's the best way to catalog and prioritize technical debt in a large codebase?▼

Technical debt cataloging structures identified issues into actionable categories, then risk-based prioritization ranks improvements by business impact and implementation effort, delivering a sequenced roadmap for systematic refactoring.

Can I use this for refactoring guidance when I have architecture diagrams and subsystem documentation?▼

Yes. This skill routes you to architecture-focused workflows when you have archaeologist outputs—subsystem catalogs, diagrams, and reports—as input prerequisites for assessment, debt identification, and improvement planning.

How do I create a structured improvement roadmap with prioritized refactoring recommendations?▼

After assessing architecture quality and cataloging technical debt, improvement roadmap generation sequences recommendations by risk level and dependency, delivering a phased plan for architectural enhancement.

When should I assess architecture versus jumping straight to refactoring?▼

Structured architecture assessment prevents costly refactoring mistakes by establishing baseline quality, exposing hidden dependencies, and grounding decisions in evidence rather than assumptions about where problems actually lie.

Related Skills

Explore More Software Engineering Skills→
tachyon-beeptachyon-beep
1

documenting-system-architecture

Synthesize subsystem catalogs and diagrams into structured architecture reports.

Community
Basic
marcius-llmusmarcius-llmus
1

decomposition-planning-roadmap

Plan and prioritize decomposition roadmaps for migrating monolithic codebases to distributed architectures.

Community
Advanced
definableaidefinableai
27

plan-project

Break down project goals into tasks, dependencies, risks, and milestones.

Official
Intermediate
vndkubivndkubi

technical-debt-analysis

Identify and prioritize technical debt with effort estimates and business impact.

Community
Advanced