architecture-status

The architecture-status skill acts as an automated health checker for the AI Software Architect framework. It scans the .architecture/ directory to assess the state of architectural decision records (ADRs), peer and specialist reviews, recalibration progress, and team composition. Designed for engineering teams and technical leads, this skill provides a centralized overview of project documentation quality, helping maintain architectural rigor throughout the software development lifecycle.

• Performs comprehensive audits of ADR files to calculate acceptance, deprecation, and proposal statuses.

• Summarizes architecture review activity, distinguishing between feature, version, and specialist review types.

• Tracks recalibration plans to monitor how architectural reviews are translated into implementation tasks.

• Analyzes documentation coverage to identify gaps in areas such as security, infrastructure, and system design.

• Generates a structured markdown report including summary metrics, recent activity logs, and actionable recommendations based on documented health indicators.

• Provides intelligent guidance to users on whether to create new ADRs, initiate reviews, or consult specialists based on current gaps.

• Operates by scanning the local .architecture/ directory; requires the AI Software Architect framework to be initialized.

• Offers health ratings ranging from Excellent to Inactive based on documentation frequency and recent updates.

• Best used at the start of a sprint, before major releases, or during project transitions to ensure alignment.

• If the framework is not detected, it prompts the user to run setup commands such as 'Setup ai-software-architect'.

• Integrates seamlessly with AI coding assistants like Claude Code, Cursor, and GitHub Copilot to maintain a single source of truth for architectural evolution.

• Inputs include the current state of files in the .architecture/ directory; outputs are plain text or markdown reports suitable for team updates or repository documentation.

• Avoids conflicting with document creation or specialized review tools by focusing strictly on diagnostic reporting and process health insights.