eng-utils

This pattern ensures that when a command declares it will spawn certain agents based on domain detection, those agents are actually spawned, and any deviations are communicated to the user.

Explore codebases and find implementation details. Use for (1) finding WHERE code lives (file paths, directory structure), (2) finding HOW code works (data flow, architecture, entry points), or (3) finding WHAT patterns exist (code examples and implementations to model after). Works on local files (fastest) or external repos via gh repo clone fallback. Adapts depth based on what is asked — specify "where", "how", or "show me examples" in your prompt.

C4 model architecture diagrams for systems. Use when asked to create architecture documentation, model a system for agent reasoning, generate C4 diagrams from code/config, or plan multi-system refactorings that need architectural context.

Explore a codebase for architectural friction (scattered concepts, shallow modules, tight coupling), quantify issues with coupling metrics, design multiple interface alternatives via parallel agents, and produce a proposal document with old/new architecture diagrams and honest pros/cons. Proposal-only — never makes code changes. Use when asked to "refactor architecture", "improve codebase structure", "deepen modules", "reduce coupling", "make code more navigable", or when /code-review repeatedly surfaces structural issues. Invocable as /refactor-architecture [scope-path].

Create architecture documentation for a system with C4 diagrams and enriched Structurizr DSL models. Use when asked to document a system's architecture, produce C4 diagrams from system names or repos, or create a comprehensive architecture README with diagrams and request flow walkthroughs. Trigger phrases include "create architecture documentation", "document this system", "generate C4 diagram", "system architecture doc". Outputs to ~/.claude/thoughts/shared/architecture/.