What problem does it solve? Before committing to a code change, teams need to understand the current architecture, affected files, and trade-offs between approaches. This Skill performs that investigation as a dedicated sub-agent and returns a structured exploration report instead of ad-hoc guesses. ## Core Features & Use Cases - Codebase Investigation: Reads entry points, related functionality, tests, and dependencies to map the current state of the system. - Approach Comparison: Produces a pros/cons/effort comparison table when multiple implementation approaches exist. - Structured Artifact Persistence: Saves an exploration.md artifact per change using engram, openspec, hybrid, or none storage modes. - Use Case: An orchestrator agent receives a feature request, delegates exploration to this sub-agent, and gets back a report listing affected files, candidate approaches, risks, and a readiness verdict for the proposal phase. ## Quick Start Ask the orchestrator to explore how a proposed feature would affect the codebase before writing a proposal.
