What problem does it solve? Before committing to a code change, teams need a disciplined way to investigate the existing codebase, compare implementation approaches, and document findings. This Skill performs that exploration phase of a Spec-Driven Development (SDD) workflow, returning a structured analysis instead of ad-hoc guesses. ## Core Features & Use Cases - Codebase Investigation: Reads entry points, related modules, tests, and existing patterns to map current architecture and affected files. - Approach Comparison: Compares multiple implementation options in a pros/cons/effort table and gives a recommendation with risks. - 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 to this exploration sub-agent, and gets back a structured report covering current state, affected files, candidate approaches, and a readiness verdict for the proposal phase. ## Quick Start Ask the orchestrator to explore how a proposed feature would fit into the current codebase before writing a proposal.
