openspec-explore

Explores ideas and investigates codebases to clarify requirements before creating OpenSpec change proposals.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-explore-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-explore-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

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 your codebase, challenges assumptions, and captures decisions as OpenSpec change artifacts before any code is written. ## Core Features & Use Cases - Guided Discovery: Asks focused questions, maps existing architecture, and surfaces risks and hidden complexity in the codebase. - ASCII Visualization: Draws system diagrams, state machines, and comparison tables to clarify design thinking. - OpenSpec Integration: Scaffolds changes via the openspec CLI and captures decisions into proposals, designs, specs, and task artifacts with explicit user confirmation. - Use Case: Before adding real-time collaboration to your app, use explore mode to compare CRDT versus presence-based approaches, inspect your current sync layer, and capture the chosen design in a change 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.

Frequently Asked Questions about openspec-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore a design idea before writing code?▼

Enter explore mode and describe your idea or problem. The skill investigates the relevant codebase, asks focused clarifying questions, and visualizes options with ASCII diagrams before you commit to an approach.

How do I create an OpenSpec change proposal from a discussion?▼

Once exploration crystallizes, confirm the scope and the skill runs openspec new change to scaffold the change, then follows CLI instructions to create proposal, design, spec, and task artifacts in dependency order.

Does openspec-explore write or modify code?▼

No. Explore mode is strictly read-only for code: it can read files, search, and run read-only commands, but never implements features. It only creates OpenSpec change artifacts after explicit user confirmation.

What is required to use the openspec explore workflow?▼

The openspec CLI must be installed, since the skill shells out to commands like openspec list, status, instructions, and new change. Without the CLI, change scaffolding and artifact tracking are unavailable.

When should I use explore mode instead of starting implementation?▼

Use it when requirements are vague, multiple architectural options exist, or you are stuck mid-implementation. It helps surface risks, compare tradeoffs, and capture decisions before committing to code changes.