architect

Audit technical debt and enforce architectural patterns across ML, Backend, and Frontend modules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ColbyRReichenbach/retentionAI --skill architect-colbyrreichenbach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/ColbyRReichenbach/retentionAI/tree/main/.claude/skills/Architect
Command: npx skills add https://github.com/ColbyRReichenbach/retentionAI --skill architect-colbyrreichenbach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides system-wide architectural oversight to prevent drift, ensure consistency across modules, and manage technical debt before it compounds.

Core Features & Use Cases

  • Technical debt auditing: Identify, classify, and prioritize debt across ML, Backend, Frontend, and data pipelines.
  • Cross-domain integration: Ensure collaboration among skills (ML ↔ Backend ↔ Frontend) and guard integration boundaries.
  • Performance & governance oversight: Monitor architectural patterns, risk, and performance implications; document decisions and ADRs for major changes.

Quick Start

Run a quarterly tech debt audit across ML, Backend, and Frontend to identify consolidation opportunities.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I audit technical debt across backend and frontend modules?

To audit technical debt across backend and frontend modules, this Skill identifies, classifies, and prioritizes debt across ML, Backend, Frontend, and data pipelines. It ensures system-wide architectural coherence before debt compounds.

What is the best way to maintain architectural coherence during cross-domain integrations?

Maintaining architectural coherence during cross-domain integrations requires guarding integration boundaries and ensuring collaboration among ML, Backend, and Frontend skills. This Skill enforces architectural patterns and checks for integration risks.

How does ADR-driven governance work for major system design decisions?

ADR-driven governance works by documenting decisions and enforcing architectural patterns for major system design changes. This Skill provides performance oversight and records ADRs to prevent architectural drift across all modules.

When do I need system architecture oversight for technical debt management?

You need system architecture oversight for technical debt management when performing quarterly audits or risk assessments for major design decisions. It prevents architectural drift and ensures consistency across modules before debt compounds.

Can I use this for risk assessments on major architectural design decisions?

Yes, you can use this for risk assessments on major architectural design decisions. It monitors performance implications, classifies technical debt, and applies ADR-driven governance to ensure architectural patterns are followed.

Does this Skill support performance oversight across data pipelines and backend systems?

Yes, this Skill supports performance oversight across data pipelines and backend systems. It monitors architectural patterns, risk, and performance implications while ensuring system-wide architectural coherence and debt management.