triage-architecture

Orchestrate four parallel sub-agents to audit architecture and integrate ticket systems.

3|2|Updated Apr 10, 2026

Search Tags:#architecture #root-cause #parallel-agents #risk-analysis #code-audit #ticketing

Ready to run

npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill triage-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-architecture
Source: https://github.com/AdamCaviness/agentic-toolkit/tree/main/skills/triage-architecture
Command: npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill triage-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates end-to-end architecture auditing by orchestrating multiple sub-agents and ticket-system integration to surface root architectural concerns.

Core Features & Use Cases

Detects the project's ticket system automatically and caches tickets to disk for offline analysis.
Spawns four parallel sub-agents focused on Safety, Correctness, Maintainability, and Completeness to scrutinize the codebase.
Builds a project map to guide auditing, assigns tickets to clusters, and surfaces consolidated findings for review.
Produces cross-cluster notes to help weave insights back into existing tickets.

Quick Start

Run the triage-architecture skill in create mode to begin auditing your project.

Frequently Asked Questions about triage-architecture

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

FAQPage Schema

How do I automate a codebase architecture audit and map findings to existing tickets?▼

Automating an architecture audit involves detecting your ticketing system, caching tickets to disk, and spawning parallel agents to assess safety, correctness, maintainability, and completeness, producing per-cluster tickets and a project map for remediation.

What is multi-cluster codebase auditing and how does it identify root-cause architecture risks?▼

Multi-cluster codebase auditing is a process that orchestrates focused sub-agents to scrutinize safety, correctness, maintainability, and completeness, surfacing root architectural concerns and generating cross-cluster notes to weave insights back into existing tickets.

How do I run an architecture audit across a project with a formal ticketing system?▼

To run an architecture audit on a ticketed project, initiate the skill in create mode; it automatically detects the ticket system, caches tickets offline, and coordinates parallel risk-analysis agents to generate consolidated findings and a project map.

Can I use parallel agents for code audits to assess maintainability and correctness simultaneously?▼

Yes, you can use parallel agents for code audits to assess maintainability and correctness simultaneously, as the workflow spawns four focused sub-agents dedicated to safety, correctness, maintainability, and completeness to scrutinize the codebase in parallel.

Does this architecture auditing workflow require a specific ticketing system to function?▼

No specific ticketing system is required, but the architecture auditing workflow applies to projects with a formal ticketing system; it automatically detects the project's ticket system and caches tickets to disk for offline analysis during the audit.

What limitations exist when auditing architecture across multiple code clusters?▼

A key limitation when auditing architecture across multiple code clusters is that the workflow requires a formal ticketing system to function, as it relies on detecting and caching tickets to disk to produce per-cluster tickets and cross-cluster notes for remediation.