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 approaches, and crystallize decisions before committing to a change proposal. ## Core Features & Use Cases - Exploration stance: Acts as a thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without following a rigid script. - Codebase grounding: Reads and maps existing architecture, integration points, and patterns to keep discussions grounded in the actual code. - 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 map the collaboration spectrum, compare CRDT versus simpler presence approaches with ASCII diagrams, then capture the chosen direction in a design document. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem before creating an OpenSpec change proposal.
