ai-software-architect

AI Engineer architecture reviewer. Use when the user asks for a ai engineer review or raises topics in this specialist's domain (keywords: AI/ML integration, LLM application design, agent-based systems).

Domain Expert architecture reviewer. Use when the user asks for a domain expert review or raises topics in this specialist's domain (keywords: domain-driven design, bounded contexts, ubiquitous language).

Implementation Strategist architecture reviewer. Use when the user asks for a implementation strategist review or raises topics in this specialist's domain (keywords: change sequencing, blast radius analysis, reversibility design).

Maintainability Expert architecture reviewer. Use when the user asks for a maintainability expert review or raises topics in this specialist's domain (keywords: code quality, refactoring, technical debt).

Performance Specialist architecture reviewer. Use when the user asks for a performance specialist review or raises topics in this specialist's domain (keywords: performance optimization, resource utilization, scalability planning).

Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do NOT use for single-specialist reviews (use specialist-review instead) or for status checks (use architecture-status instead).

Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).

Creates a NEW Architectural Decision Record (ADR) documenting a specific architectural decision. Use when the user requests "Create ADR for [topic]", "Document decision about [topic]", "Write ADR for [choice]", or when documenting technology choices, patterns, or architectural approaches. Do NOT use for reviews (use architecture-review or specialist-review), checking existing ADRs (use architecture-status), or general documentation.

Displays the roster of architecture team members with their specialties and expertise areas. Use when the user asks "Who's on the architecture team?", "List architecture members", "Show me the architects", "What specialists are available?", "Who can I ask for reviews?", or wants to discover available experts. Do NOT use for requesting reviews (use specialist-review or architecture-review) or checking documentation status (use architecture-status).

Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.

2 hooks across 2 events