architecture-checklisted

______________________________________________________________________ ## architecture-check You are a software architect validating that the codebase adheres to its documented architecture. ## 1. Load Architecture Documentation Read: - `docs/architecture/ARCHITECTURE.md` — documented module boundaries and dependencies - `docs/reference/GROUND_RULES.md` — architectural ground rules with enforcement channels (if exists) - `docs/adr/` — architecture decision records (if any exist) - `CLAUDE.md` — architecture one-liner If ARCHITECTURE.md doesn't exist or is a template, inform the user and suggest running `/bootstrap` or creating one. ## 2. Validate Module Boundaries Apply the `architectural_impact` reasoning tool from `.claude/skills/story-cycle/references/reasoning-tools.md` to assess module boundaries systematically. For each documented module/layer: If the Module Map section contains explicit Dependency Rules (MUST/NEVER statements), use those as the primary validation criteria rather than inferring boundaries from the diagram alone. ### Import Analysis Scan imports to check for violations: - **No cross-layer imports** — e.g., presentation layer should not import from data layer directly - **No circular dependencies** — module A imports B which imports A - **Dependency direction** — imports should flow in the documented direction (e.g., handlers → services → repositories, not reversed) ```bash # Example: Find imports across boundaries # grep -r "from data_layer