openspec-explore

Explores ideas, investigates codebases, and clarifies requirements through conversational analysis.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yujikawa/modscape --skill openspec-explore-yujikawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/yujikawa/modscape/tree/main/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/yujikawa/modscape --skill openspec-explore-yujikawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned solutions. This Skill provides a dedicated thinking mode where you can explore ideas, investigate the codebase, and clarify requirements without writing any code. ## Core Features & Use Cases - Exploratory Thinking Partner: Acts as a curious, adaptive collaborator that asks clarifying questions, challenges assumptions, and surfaces risks rather than following a rigid script. - Codebase Investigation: Reads files, maps existing architecture, finds integration points, and grounds discussions in the actual code. - Visual Reasoning: Uses ASCII diagrams liberally to sketch system architectures, state machines, data flows, and comparison tables. - OpenSpec Integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions into specs, design docs, or task lists. - Use Case: Before building a real-time collaboration feature, enter explore mode to map the collaboration spectrum, compare CRDT versus simpler presence approaches, and capture the resulting design decisions in an OpenSpec change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem 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 software idea before implementing it?▼

Enter explore mode and describe your idea or problem in natural language. The assistant investigates the codebase, asks clarifying questions, sketches ASCII diagrams, and compares options without writing any implementation code.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking stance for investigating problems and clarifying requirements before or during a change. It reads OpenSpec artifacts like proposals and designs, and offers to capture decisions, but never implements features.

Can explore mode write code or implement features?▼

No, explore mode explicitly forbids writing code or implementing features. It may only read files, search code, and create OpenSpec artifacts such as proposals, designs, and specs when the user asks.

Does openspec-explore require the openspec CLI?▼

Yes, the skill declares compatibility with the openspec CLI. It uses commands like openspec list --json to detect active changes and reads artifacts under the openspec/changes directory for context.

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

Exit explore mode when the problem and approach have crystallized and you are ready to implement. The assistant will offer to create a change proposal once insights solidify, but the decision always remains with the user.