What problem does it solve? Architecture knowledge usually scatters across repositories, wikis, and chat threads, so teams repeat decisions, lose reusable-component evidence, and start risky initiatives without an architecture check. This Skill centralizes durable cross-project architecture memory in a portable Markdown/Obsidian home and enforces explicit Architecture Gates before implementation. ## Core Features & Use Cases - Architecture Preflight and Gates: Evaluate an Epic or plan before coding, write a bounded Architect Addendum, and set the gate to passed or blocked so downstream roles stop when required. - Evidence-Based Assessments: Run ATAM-lite assessments with quality scenarios, material risks, and concise briefs, recording only material deltas instead of repeating surveys. - Component Governance: Register reusable components, track their lifecycle from candidate to stable, and record project-by-project application results and extraction contracts. - Deterministic CLI: A Python CLI initializes the architecture home, creates validated records with stable IDs, rebuilds indexes, checks links, and enforces report word limits. - Use Case: Before starting a migration Epic, run the preflight workflow to check reusable components and material risks, then record the gate result; after release, run closeout to capture only the architectural delta. ## Quick Start Ask the agent to run an architecture preflight on your current Epic plan and initialize the architecture home using the bundled CLI.
