architecture-audit

Name: architecture-audit
Availability: InStock
Author: oduffy

Select the highest-priority system for an architectural audit and orchestrate reviewer analysis.

5|2|Updated Mar 20, 2026

Search Tags:#dependency analysis #architecture audit #system health #review orchestration #codebase governance #spinoff planning #atlas metadata

Ready to run

npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill architecture-audit-dbc-oduffy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-audit
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/architecture-audit
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill architecture-audit-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

It helps you keep complex systems healthy by selecting the right target for an architectural audit and producing actionable, scoped spinoff candidates—without changing the codebase.

Core Features & Use Cases

Rotational target selection: Picks the highest-priority system from the health ledger using staleness, criticality, open items, and roadmap-activity signals.
Domain reviewer dispatch & grading: Sends the selected system to the appropriate domain reviewer (or runs a Haiku→Sonnet pre-digestion for larger systems) and ensures backstops for quality.
Spinoff-candidate packaging: Converts audit findings into a disposition ladder (immediate executor for trivial non-structural items; PM-gated spinoff candidates for structural work; or escalation to /plan) while keeping the audit itself code-free.

Quick Start

Run /architecture-audit to perform a rotational targeted audit of the highest-priority system.

Frequently Asked Questions about architecture-audit

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

FAQPage Schema

How do I perform an architecture audit without modifying the codebase?▼

An architecture audit evaluates system health and produces spinoff-ready findings while enforcing non-inline edits, ensuring your codebase governance review remains completely code-free. It orchestrates reviewer analysis to identify structural issues safely.

What is rotational target selection for system health monitoring?▼

Rotational target selection picks the highest-priority system for an architectural audit using staleness, criticality, open items, and roadmap-activity signals. This weighting ensures ongoing system health monitoring focuses on the most needy codebase.

How do I prioritize which system to audit first using dependency analysis?▼

You prioritize audits by applying health-ledger and roadmap-activity weighting to evaluate system staleness and criticality. This dependency analysis identifies the highest-priority system for targeted rotational audits based on open items.

Do I need jq installed to run an architecture audit?▼

Yes, you need jq installed because it is a required dependency for parsing atlas metadata and health-ledger data during the architecture audit. This command-line JSON processor enables the review orchestration logic.

Can I run a targeted re-audit on a specific system instead of a rotational one?▼

Yes, you can run a targeted re-audit by providing a specific system as an argument, which overrides the rotational targeting. This updates the Last targeted audit clock while preserving the Last full audit timestamp.

What's the best way to package audit findings into actionable spinoff candidates?▼

The best way is converting audit findings into a disposition ladder: immediate executor for trivial non-structural items, PM-gated spinoff candidates for structural work, or escalation to planning. This packaging keeps the architectural review code-free.