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 that investigates the codebase, visualizes options, and captures decisions as OpenSpec change artifacts without writing implementation code. ## Core Features & Use Cases - Guided Exploration: Acts as a thinking partner that asks focused questions, challenges assumptions, and surfaces risks before any code is written. - Codebase Grounding: Reads existing specs, changes, and project context via the openspec CLI so discussions are anchored in the actual architecture. - Artifact Capture: Scaffolds new changes with openspec new change and records decisions in proposals, designs, specs, and task files after explicit user confirmation. - Use Case: A developer considering real-time collaboration can explore the tradeoffs between presence indicators, shared cursors, and CRDT-based sync, then capture the chosen direction as an OpenSpec proposal. ## Quick Start Ask the assistant to enter explore mode and think through whether your planned feature should use SQLite or Postgres before creating a change proposal.
