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: Acts as a curious thinking partner that asks clarifying questions, challenges assumptions, and follows interesting threads without forcing a fixed workflow. - Codebase grounding: Reads files, searches code, and maps existing architecture to ground discussions in reality rather than theory. - ASCII visualization: Sketches system diagrams, state machines, data flows, and comparison tables to clarify complex thinking. - OpenSpec integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions in the right artifacts. - Use Case: Before adding real-time collaboration to your app, enter explore mode to map the collaboration spectrum, compare CRDT versus simpler presence approaches, and crystallize the scope into a change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem before writing any code.
