openspec-explore

Explores ideas and investigates codebases as a thinking partner before creating OpenSpec change proposals.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-explore-hongwt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/hongwt/dsplm-monitor/tree/main/.pi/skills/openspec-explore
Command: npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-explore-hongwt

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 dedicated explore mode where you can think through ideas, investigate the codebase, compare options, and clarify requirements without writing any application code. ## Core Features & Use Cases - Exploratory Thinking Partner: Asks clarifying questions, challenges assumptions, surfaces risks, and visualizes concepts with ASCII diagrams instead of following a rigid script. - Codebase Investigation: Maps existing architecture, finds integration points, and grounds discussions in the actual code using the openspec CLI. - OpenSpec Artifact Capture: When insights crystallize, scaffolds changes with openspec new change and captures decisions into proposals, designs, specs, and tasks. - Use Case: You are debating whether to use SQLite or Postgres for a CLI tool. Enter explore mode, discuss constraints, view a comparison diagram, and once decided, capture the decision into a design.md artifact. ## Quick Start Ask the assistant to enter explore mode to think through adding real-time collaboration to your project before creating any 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 an idea before implementing it with OpenSpec?▼

Invoke explore mode and describe your idea or problem. The assistant investigates the codebase, asks clarifying questions, and visualizes options with diagrams, then offers to capture decisions into a change proposal when you are ready.

Can explore mode write code or implement features?▼

No. Explore mode is strictly for thinking and investigation; it never writes application code. It can only create OpenSpec artifacts like proposals, designs, and specs when you explicitly ask to capture decisions.

What is required to use the openspec explore workflow?▼

The openspec CLI must be installed, since the skill runs commands like openspec list, new change, status, and instructions. Without a registered store, commands operate on the nearest local openspec directory.

How does explore mode handle multiple OpenSpec stores?▼

It runs openspec store list --json to discover registered store ids, then appends --store <id> to commands that read or write specs and changes. The selected store flag stays sticky for the rest of the workflow.

When should I not use explore mode?▼

Avoid it when you already have clear requirements and want direct implementation. Explore mode deliberately avoids coding, so for execution tasks you should exit explore mode and create a change proposal first.