audit-architecture

Compare intended architecture against the actual codebase to detect drift.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ian97531/goodplan --skill audit-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-architecture
Source: https://github.com/ian97531/goodplan/tree/main/skills/audit-architecture
Command: npx skills add https://github.com/ian97531/goodplan --skill audit-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compare intended architecture against the actual codebase and surface drift, guiding proposals for improvements and side quests.

Core Features & Use Cases

  • Side-effect aware architecture drift detection across project and epic levels.
  • Automated gap analysis, reconciliation, and architecture reassessment with actionable recommendations.
  • Generates structured audit reports and decision records to drive maturity changes.

Quick Start

Run the audit-architecture process to compare the project's architecture with the current codebase and generate an architecture audit report.

Note: This version includes optional steps for fitness/invariant checks and project health synchronization.

Frequently Asked Questions about audit-architecture

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

FAQPage Schema
What is architecture drift detection and how does it compare intended design against actual code?

Architecture drift detection identifies discrepancies between intended project or epic architecture and the actual codebase. It performs gap analysis, reconciles findings, and generates structured audit reports with actionable recommendations to resolve deviations.

How do I audit my codebase for architecture maturity and decision traceability?

To audit architecture maturity, run the audit process against architecture files and maturity conventions. It enforces decision traceability, performs fitness and invariant checks, and produces structured reports alongside decision records to guide maturity changes.

Do I need predefined architecture decisions and maturity conventions before running an architecture audit?

Yes, architecture drift detection requires predefined inputs including architecture files, decisions, and maturity conventions. These establish the intended baseline needed to compare against the actual codebase and generate accurate reconciliation findings.

Can I perform architecture reassessment and gap analysis at both project and epic levels?

Yes, architecture reassessment and side-effect aware drift detection operate across both project and epic levels. The audit scope covers gap analysis, fitness checks, and side-quest proposals to ensure comprehensive architecture alignment.

What is the best way to resolve architecture drift and project health synchronization issues?

The best way to resolve architecture drift is through automated gap analysis and reconciliation. The audit generates structured decision records and side-quest proposals, driving maturity changes while optionally synchronizing project health and invariant checks.

When should I avoid using automated architecture drift detection for my subsystems?

You should avoid automated architecture drift detection if your project lacks documented architecture files, decision records, or established maturity conventions, as these inputs are strictly required to establish the intended baseline for accurate gap analysis.