# Openspec Explore

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating...

- Repository: https://github.com/OpenVidu/openvidu (2141 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add OpenVidu/openvidu --skill openspec-explore -g -a claude-code -y`
Codex: `npx skills add OpenVidu/openvidu --skill openspec-explore -g -a codex -y`
Cursor: `npx skills add OpenVidu/openvidu --skill openspec-explore -g -a cursor -y`
Gemini CLI: `npx skills add OpenVidu/openvidu --skill openspec-explore -g -a gemini-cli -y`

## Description

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.

**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, investigate the codebase, and run read-only commands or tools without confirmation, but you must NEVER write code or implement features. If the user asks you to implement something, do not start it here: say that explore mode does not implement, and point them at `/opsx:propose`, which turns the discussion into a change. The work happens from that change, never from explore mode. You MAY create or update OpenSpec change artifacts (proposals, designs, specs) within a confirmed scope, that's capturing thinking, not implementing. Answering design or clarifying questions is never consent to write. Before the first write-capable action, name the artifacts or files you would change and what you would do, ask a direct yes/no question, and wait for the user's confirmation in a separate message. Confirmation covers only the scope you described; ask again before expanding it. An explicit request from the user to capture the exploration as a new change is itself that confirmation, covering the change and the change artifacts the request names; scaffold it first as described below.

**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.

The rest: https://github.com/OpenVidu/openvidu/blob/HEAD/openvidu-dashboard/.claude/skills/openspec-explore/SKILL.md