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 that investigates the codebase, visualizes options, and captures decisions as OpenSpec change artifacts without writing production code. ## Core Features & Use Cases - Explore Mode Stance: Acts as a curious thinking partner that asks questions, challenges assumptions, and surfaces risks instead of implementing code. - OpenSpec Integration: Reads project context via the openspec CLI, scaffolds new changes with openspec new change, and captures insights into proposals, designs, specs, and tasks. - ASCII Visualization: Draws plain-ASCII diagrams, state machines, and comparison tables to clarify architecture and tradeoffs. - Use Case: A developer unsure whether to use SQLite or Postgres for a CLI tool enters explore mode, gets a grounded comparison based on project constraints, and captures the decision in design.md once confirmed. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem before creating an OpenSpec change proposal.