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 thinking-partner mode for exploring ideas, investigating codebases, and clarifying requirements before or during a change, without writing any application code. ## Core Features & Use Cases - Explore Mode Stance: Acts as a curious thinking partner that asks questions, challenges assumptions, compares options, and surfaces risks instead of following a fixed script. - Codebase Investigation: Reads files, maps architecture, finds integration points, and grounds discussions in the actual code while never implementing features. - OpenSpec Integration: Checks active changes via the openspec CLI, scaffolds new changes with openspec new change, and captures decisions into proposals, designs, specs, and task artifacts. - ASCII Visualization: Uses diagrams, state machines, and comparison tables to clarify complex thinking. - Use Case: A developer considering real-time collaboration can explore the tradeoffs between presence indicators, shared cursors, and CRDT-based sync, then capture the decision as an OpenSpec change proposal once the direction crystallizes. ## Quick Start Ask the assistant to enter explore mode and think through whether Postgres or SQLite fits your CLI tool before creating a change proposal.
