Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

Explore Internal Codebase Exploration Meta skill for exploring an internal codebase at varying depths. READ ONLY workflow no code changes. Usage Question Flow (No Arguments) If the user types just /explore with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase. Phase 0: Workflow Selection Mapping: "Help me choose" → Continue to Phase 1 4 questions "Quick" → Set depth=quick, skip to Phase 2 (scope) "Deep" → Set depth=deep, skip to Phase 2 (scope) "Architecture" → Set depth=architecture, skip to Phase 2 (scope) If Answer is Unclear (via "Other"): Phase 1: Exploration Goal Mapping: "Get oriented" → quick depth "Understand how" → deep depth "Map architecture" → architecture depth "Find where" → quick with focus Phase 2: Scope If "Specific directory" or "Specific concept" → ask follow up for the path/keyword. Phase 3: Output Format Mapping: "Documentation file" → output doc "Handoff for implementation" → output handoff Phase 4: Entry Point (Architecture only) If architecture depth selected: Summary Before Execution Depths Depth Time What it does quick ~1 min tldr explorer only fast structure overview deep ~5 min onboard + tldr explorer + research codebase + write doc architecture ~3 min tldr arch + call graph + layer mapping + circular dep detection Options Option Description Example focus "area" Focus on specific area focus "auth" , focus "api" output handoff Create handoff for next agent output handoff output doc Create documentation file output doc entry "func" Start from specific entry point entry "main" , entry "process request" Examples Workflow Details Quick Depth Fast structure overview using tldr explorer. Best for: Initial orientation Quick questions about structure Finding where things are Steps: 1. Run tldr tree for file structure 2. Run tldr structure for codemaps 3. If focus provided, run tldr search for targeted results 4. Return summary Commands: Deep Depth Comprehensive exploration with documentation output. Best for: First time in a codebase Preparing for major work Creating reference documentation Steps: 1. Check if onboarded (look for .claude/cache/tldr/ ), if not run onboard 2. Run tldr explorer for structure 3. Spawn research codebase agent for patterns 4. Write findings to doc or handoff Subprocess: Architecture Depth Architecture focused analysis with layer detection. Best for: Understanding system boundaries Preparing for refactoring Identifying coupling issues Steps: 1. Run tldr arch for layer detection 2. Run tldr calls for cross file call graph 3. Analyze entry/middle/leaf layers 4. Detect circular dependencies 5. Map architectural boundaries Commands: Output Structure: Output Formats output doc Creates: thoughts/shared/research/YYYY MM DD explore {focus}.md output handoff Creates: thoughts/shared/handoffs/{session}/explore {focus}.yaml Integration with /build The explore skill is designed to feed into /build brownfield : Implementation When user invokes /explore <depth [options] : Parse Arguments Execute Based on Depth Quick: Deep: Architecture: Key Principles 1. READ ONLY This skill never modifies code 2. Uses scout, not Explore Per project rules, scout (Sonnet) over Explore (Haiku) 3. Token efficient Uses tldr commands (95% savings over raw reads) 4. Outputs to shared locations thoughts/shared/research/ or handoff directory 5. Entry point to /build Exploration handoffs feed into brownfield builds Related Skills Skill When to Use tldr explorer Direct tldr commands (used internally by explore) tldr code Specific analysis commands (cfg, dfg, slice) onboard First time project setup (used by deep depth) research codebase Pattern documentation (used by deep depth) create handoff Handoff format (used by output handoff) Troubleshooting tldr not found: No Python files found: Empty architecture output: