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 investigate the codebase, compare design options, and crystallize requirements before committing to a change proposal. ## Core Features & Use Cases - Exploratory Thinking Mode: Acts as a thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without writing any implementation code. - Codebase Investigation: Maps existing architecture, finds integration points, and grounds discussions in the actual code rather than theory. - OpenSpec Integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions into specs, design.md, tasks.md, or proposal.md. - Use Case: Before adding real-time collaboration to your app, enter explore mode to visualize the collaboration spectrum (presence, cursors, CRDTs), compare tradeoffs, and only then create a formal change proposal. ## Quick Start Ask the assistant to enter explore mode to think through a feature idea or investigate a problem in the codebase before implementing it.
