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 upfront investigation as a delegated sub-agent within a spec-driven development (SDD) workflow, returning a structured analysis instead of ad-hoc notes. ## Core Features & Use Cases - Codebase Investigation: Reads entry points, related functionality, tests, and existing patterns to map the current state and affected areas. - Approach Comparison: Compares multiple implementation options with pros, cons, and effort estimates, plus a recommendation and risk list. - Artifact Persistence: Saves an exploration.md artifact per named change, supporting 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 structured report covering current state, affected files, candidate approaches, and readiness for a formal proposal. ## Quick Start Ask the orchestrator to explore how a proposed feature would affect the codebase before drafting a change proposal.
