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 dedicated thinking mode where you can explore ideas, investigate the codebase, compare options, and surface risks before committing to a change proposal. ## Core Features & Use Cases - Exploration stance without implementation: Read files, search code, and map architecture while being explicitly blocked from writing application code. - OpenSpec integration: Detects active changes via the openspec CLI, reads existing artifacts (proposals, designs, specs), and offers to capture decisions in the right artifact. - Visual thinking: Uses ASCII diagrams, comparison tables, and state machines to clarify architecture, tradeoffs, and data flows. - Use Case: Before adding real-time collaboration to your app, enter explore mode to map the collaboration spectrum (presence, cursors, CRDTs), investigate your current architecture, and crystallize the approach into a change proposal. ## Quick Start Ask the assistant to enter explore mode and think through whether SQLite or Postgres fits your CLI tool before writing any code.
