openspec-explore

Explores ideas, investigates codebases, and clarifies requirements before creating OpenSpec change proposals.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-explore-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-explore-codercoco-studios

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 thinking mode where you can explore ideas, investigate the codebase, compare options, and surface risks before committing to a change proposal. ## Core Features & Use Cases - Explore Mode Stance: Acts as a thinking partner that asks questions, challenges assumptions, and visualizes concepts with ASCII diagrams, without writing any implementation code. - OpenSpec Integration: Reads existing changes, specs, and project context via the openspec CLI, and offers to capture decisions into proposals, designs, specs, or task lists. - Codebase Grounding: Investigates actual code to map architecture, find integration points, and surface hidden complexity relevant to the discussion. - Use Case: Before adding real-time collaboration to your app, enter explore mode to compare presence indicators, cursor sharing, and CRDT approaches, then capture the chosen direction in a design artifact. ## Quick Start Ask the assistant to enter explore mode and think through an idea or problem, for example by describing a vague feature idea or a specific technical problem you want to investigate.

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 feature idea before writing code?

Enter explore mode and describe your idea, even vaguely. The assistant acts as a thinking partner, asking clarifying questions, drawing ASCII diagrams of options, and investigating the codebase to ground the discussion before any implementation begins.

What is OpenSpec explore mode used for?

Explore mode is a thinking stance for investigating problems and clarifying requirements without implementing anything. It can read existing OpenSpec changes and specs, and offers to capture decisions into proposals, designs, or task lists when insights crystallize.

Can explore mode write code or implement features?

No, explore mode never writes application code or implements features. It may only create OpenSpec artifacts such as proposals, designs, and specs when you ask, since capturing decisions is considered thinking, not implementing.

Does openspec-explore require the openspec CLI?

Yes, the Skill requires the openspec CLI to be installed. It uses commands like openspec list, status, and store list to discover active changes, read project context from config.yaml, and resolve artifact paths.

When should I exit explore mode and create a change proposal?

Exit explore mode when the problem and approach feel crystallized and you are ready to implement. The assistant will offer to create a change proposal when insights solidify, but the decision to formalize is always yours.