What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned features. This Skill provides a dedicated thinking mode where you can explore ideas, investigate the codebase, and clarify requirements without writing any application code. ## Core Features & Use Cases - Exploration Stance: Acts as a curious thinking partner that asks questions, challenges assumptions, and surfaces risks instead of following a fixed script. - Codebase Investigation: Reads files, maps architecture, finds integration points, and visualizes findings with ASCII diagrams, state machines, and comparison tables. - OpenSpec Integration: Checks existing changes via openspec list --json, reads proposal/design/tasks artifacts, and offers to capture decisions into specs, design.md, or proposal.md. - Use Case: Before building a real-time collaboration feature, enter explore mode to compare approaches (presence indicators vs. CRDTs), diagram the architecture, and only then create a formal change proposal. ## Quick Start Ask the agent to enter explore mode and think through your idea, for example by saying: explore whether we should use Postgres or SQLite for our CLI tool before creating a change proposal.
