Spell Deep Dive

## Summary

**Codebase exploration and program comprehension.** Systematically explores a module, feature, or subsystem and produces a structured architecture map — entry points, data flow, key abstractions, and design decisions. Uses top-down reading strategy: start at entry points, trace inward.

**Arguments:** `$ARGUMENTS` (required) - File path, module name, feature description, or question (e.g., "how does auth work?")

**Output:** Structured architecture report with overview, diagram, key files, data flow, and design decisions

---

## Skill References

Before proceeding, load the relevant skill documents for reference:

Read the following files from the repository root:
- `docs/skills/program-comprehension.md`
- `docs/skills/architecture-patterns.md`

---

## Process

### Step 1: Determine Scope

Parse `$ARGUMENTS` to figure out what to explore:

| Input type | Action |
|------------|--------|
| File or directory path | Explore that module — its purpose, connections, and architecture |
| Feature or component name | Find where it's implemented, trace its boundaries |
| Question ("how does X work?") | Find entry points for X, trace the implementation |
| Vague or broad | Narrow scope before proceeding (see below) |

If the scope is unclear, ask the user to specify: a file/directory path, a feature name, a question about the code, or whether they want a high-level architecture overview.

**Output the scope:**