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 structured thinking partner mode that helps you explore ideas, investigate the codebase, and crystallize requirements before committing to a change. ## Core Features & Use Cases - Exploration Stance: Acts as a curious thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without following a rigid script. - Codebase Investigation: Reads files, maps architecture, finds integration points, and grounds discussions in the actual code rather than theory. - ASCII Visualization: Liberally uses diagrams, state machines, comparison tables, and architecture sketches to clarify complex thinking. - 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 building a real-time collaboration feature, use explore mode to map the collaboration spectrum (presence, cursors, CRDT sync), compare tradeoffs, and then formalize the decision into an OpenSpec change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem before creating an OpenSpec change proposal.
