architecture-introspector

# Architecture Introspector

Systematically analyze software architectures using first principles thinking, applying SpaceX's 5-step engineering methodology combined with software modularity principles to identify unnecessary complexity, validate architectural decisions, and recommend improvements.

## Purpose

This skill provides a rigorous, principle-based framework for evaluating software architectures. It challenges inherited assumptions, identifies unjustified complexity, and applies the "delete first, optimize later" philosophy to architecture. The goal is to achieve simple, justified architectures where every component earns its existence through actual need rather than hypothetical future requirements.

## When to Use This Skill

Use this skill when:

- **Analyzing existing architectures** - Understanding whether current architectural patterns are justified
- **Evaluating architectural decisions** - Questioning whether a proposed abstraction/layer/pattern is necessary
- **Identifying technical debt** - Finding components that add complexity without proportional value
- **Planning refactoring efforts** - Determining what to delete, simplify, or consolidate
- **Onboarding to codebases** - Understanding architectural rationale and identifying areas for improvement
- **Code review of architectural changes** - Ensuring new abstractions meet the 2+ consumer threshold
- **Modernization efforts** - Deciding what to keep, kill, or consolidate during rewrites

## Core Philosophy

### SpaceX's 5-Step Engineering Methodology

1. **Question Every Requirement** - Trace decisions to their origins, challenge assumptions
2. **Delete the Part or Process** - Remove first, optimize never (if it shouldn't exist)
3. **Simplify and Optimize** - Only after deletion is complete
4. **Accelerate Cycle Time** - Speed up validated, simplified processes
5. **Automate** - Last step only, after deletion and simplification

### Software Modularity Principle

**"Modularity without reuse is b