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, compare options, and clarify requirements before or during a change—without writing any implementation code. ## Core Features & Use Cases - Guided Discovery: Asks focused, dependency-aware questions grounded in your actual codebase and existing OpenSpec artifacts, using ASCII diagrams to visualize architecture, state machines, and tradeoffs. - OpenSpec Integration: Reads project context, active changes, and specs via the openspec CLI, and can scaffold new changes and capture decisions into proposals, designs, specs, and task lists with explicit user confirmation. - Strict Guardrails: Never implements code; read-only investigation runs freely while any write action requires naming the artifacts and getting a direct yes/no confirmation first. - Use Case: While planning a new authentication feature, use explore mode to map the current auth flow, compare OAuth versus magic-link approaches, and capture the resulting decisions into a change proposal and design document. ## Quick Start Ask the assistant to enter explore mode and help you think through a feature idea or investigate a problem in your codebase before creating a change proposal.
