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 thinking mode where you can explore ideas, investigate the codebase, and clarify requirements before committing to a change proposal. ## Core Features & Use Cases - Exploration Stance: Acts as a thinking partner that asks questions, challenges assumptions, compares options, and visualizes concepts with ASCII diagrams instead of following a fixed workflow. - OpenSpec Integration: Checks existing changes via openspec list --json, reads proposals, designs, specs, and tasks, and offers to capture decisions into the right artifacts. - Implementation Guardrails: Reads and investigates code but never writes application code, keeping exploration separate from implementation. - Use Case: You are unsure whether to use Postgres or SQLite for a CLI tool. Enter explore mode, discuss constraints, view a comparison table, and then optionally capture the decision in design.md. ## Quick Start Ask the assistant to enter explore mode to think through your idea or problem before creating an OpenSpec change proposal.
