openspec-explore

Explores ideas and clarifies requirements through OpenSpec-guided thinking sessions.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-explore-gqadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-explore
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-explore-gqadonis

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 helps you explore ideas, investigate codebases, and clarify requirements before or during a change, without writing any implementation code. ## Core Features & Use Cases - Explore Mode Thinking: Acts as a curious, non-prescriptive thinking partner that asks questions, challenges assumptions, and surfaces risks using ASCII diagrams and codebase investigation. - OpenSpec Integration: Reads existing changes via the openspec CLI, scaffolds new changes with openspec new change, and captures decisions into proposals, designs, specs, and task artifacts. - Multi-Store Support: Discovers registered OpenSpec stores with openspec store list --json and applies sticky --store <id> scoping across all spec commands. - Use Case: Before building a real-time collaboration feature, use this Skill to map the collaboration spectrum, compare CRDT versus cursor-based approaches, and capture the resulting design decisions into an OpenSpec change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea, for example by saying you want to explore adding real-time collaboration 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 feature idea before implementing it?

Invoke explore mode and describe your idea in free form. The Skill investigates the codebase, draws ASCII diagrams, compares options, and offers to capture crystallized decisions into an OpenSpec change proposal when you are ready.

How do I create an OpenSpec change proposal from a conversation?

Ask the Skill to capture the exploration as a new change. It runs openspec new change to scaffold the change, then follows openspec status and openspec instructions output to create requested artifacts like proposal.md, design.md, and specs in dependency order.

Can explore mode write code or implement features?

No. Explore mode is strictly for thinking and investigation. It can read files, search code, and create OpenSpec artifacts such as proposals and specs, but it will remind you to exit explore mode before any implementation work.

Does openspec-explore work with multiple OpenSpec stores?

Yes. It runs openspec store list --json to discover registered stores, then appends the selected --store id to all spec and change commands. Without a store, commands act on the nearest local openspec directory.

What are the limitations of explore mode?

Explore mode has no fixed workflow or required outputs, so it does not replace structured planning on its own. It also depends on the openspec CLI being installed and cannot scaffold changes manually without it.