openspec-explore

Enter openspec explore mode to discuss the problem, inspect the codebase, and compare options conversationally. When decisions crystallize, ask to capture the exploration as a new change, which scaffolds it with openspec new change and writes the confirmed artifacts.

No, explore mode never writes code or implements features. It only reads files, runs read-only commands, and creates OpenSpec change artifacts within a confirmed scope. Implementation is handed off to the openspec-propose and openspec-apply-change workflows.

The skill runs openspec list --json and checks the root field. If root is null and you explicitly requested OpenSpec, it asks whether to run openspec init, target a registered store, or continue without OpenSpec, and never creates the root as a side effect.

If your work lives in a standalone registered store, the skill runs openspec store list --json to find store ids, then appends --store <id> to every spec and change command. The selected store stays sticky for the rest of the workflow.

Before the first write-capable action, such as openspec new change or editing an artifact, it names the files and proposed changes and waits for an explicit yes. Confirmation covers only the described scope, and answering design questions never counts as consent.