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 explore mode where the AI acts as a thinking partner—investigating the codebase, visualizing architecture, and clarifying requirements—without writing any implementation code. ## Core Features & Use Cases - Exploration-Only Stance: Reads files, searches code, and investigates the codebase while strictly refusing to implement features, keeping thinking separate from coding. - Visual Thinking: Produces ASCII diagrams, state machines, data flows, and comparison tables to clarify architecture and tradeoffs. - OpenSpec Integration: Checks active changes via openspec list --json, reads existing change artifacts, and offers to capture decisions into proposals, designs, specs, or tasks. - Use Case: A developer unsure whether to use SQLite or Postgres for a CLI tool enters explore mode, gets a constraint-driven comparison grounded in their actual context, then captures the decision in design.md before starting a change proposal. ## Quick Start Ask the AI to enter explore mode and think through your idea or problem, for example by saying: explore whether we should add real-time collaboration to our editor before I write any code.
