What problem does it solve? Before committing to a code change, teams need a structured analysis of the current codebase, affected files, and viable approaches. This Skill performs that exploration phase of spec-driven development (SDD), returning a consistent, structured report instead of ad-hoc investigation notes. ## Core Features & Use Cases - Codebase Investigation: Reads entry points, related functionality, tests, and dependencies to map current architecture and affected files. - Approach Comparison: Compares multiple implementation options with pros, cons, and effort estimates in a standardized table. - Structured Artifact Output: Produces a fixed-format exploration report (current state, affected areas, approaches, recommendation, risks) and optionally persists it as exploration.md via engram, openspec, hybrid, or none storage modes. - Use Case: An orchestrator agent receives a feature request, delegates to this sub-agent, and gets back a concise analysis stating which files are affected, two or three candidate approaches, a recommendation, and whether the topic is ready for a formal proposal. ## Quick Start Ask the orchestrator to explore how a new feature would fit into the current codebase before writing a proposal.
