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 - Exploratory Thinking Partner: Engages in open-ended discussion with ASCII diagrams, comparison tables, and architecture sketches to clarify problems without writing any application code. - Codebase Investigation: Reads files, maps existing architecture, finds integration points, and surfaces hidden complexity to ground discussions in reality. - OpenSpec Integration: Checks active changes via the openspec CLI, reads existing proposals and specs, and offers to capture decisions into design.md, specs, tasks.md, or proposal.md artifacts. - Use Case: Before building a real-time collaboration feature, use explore mode to map the spectrum from presence indicators to CRDTs, compare tradeoffs, and then crystallize the decision into a formal change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem, for example by describing a vague feature idea or a specific technical problem you want to investigate before implementing.
