What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned requirements. This Skill provides a structured exploration mode where you can think through ideas, investigate the codebase, compare options, and clarify requirements before committing to a change. ## Core Features & Use Cases - Exploration stance: Acts as a curious thinking partner that asks questions, challenges assumptions, and surfaces risks without following a rigid script. - Codebase grounding: Reads files and maps existing architecture, integration points, and patterns to ground discussions in reality. - ASCII visualization: Draws system diagrams, state machines, data flows, and comparison tables to clarify thinking. - OpenSpec integration: Detects active changes via the openspec CLI, reads project context and rules, and can scaffold new changes with openspec new change when insights crystallize. - Use Case: You are unsure whether to use Postgres or SQLite for a CLI tool. Enter explore mode, discuss constraints, view a comparison table, and only then capture the decision in a design artifact. ## Quick Start Ask the assistant to enter explore mode and think through whether your planned feature should use a particular architecture before writing any code.
