openspec-explore

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

4|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-explore-jin1c-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Jin1c-3/obsidian-advanced-maps/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-explore-jin1c-3

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 the AI acts as a thinking partner—investigating the codebase, comparing options, and clarifying requirements—without writing any implementation code. ## Core Features & Use Cases - Open-ended exploration: Asks clarifying questions, challenges assumptions, and surfaces risks using ASCII diagrams to visualize architecture, state machines, and tradeoffs. - Codebase grounding: Reads files and maps existing architecture to ground discussions in the actual code rather than theory. - OpenSpec integration: Checks active changes via the openspec CLI, scaffolds new changes with openspec new change, and captures decisions into proposals, designs, specs, and tasks artifacts. - Use Case: Before adding real-time collaboration to your app, enter explore mode to map the collaboration spectrum (presence, cursors, CRDTs), investigate your current sync architecture, and capture the chosen approach as an OpenSpec change proposal. ## Quick Start Ask the AI to enter explore mode and think through whether SQLite or Postgres fits your CLI tool 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 an idea before implementing it with OpenSpec?

Invoke explore mode and describe your idea or problem. The AI investigates the codebase, asks clarifying questions, and visualizes options with diagrams, then offers to scaffold a change proposal with `openspec new change` when thinking crystallizes.

What is the difference between explore mode and implementing a change?

Explore mode is strictly for thinking: reading code, comparing options, and capturing decisions as OpenSpec artifacts. It never writes application code; implementation happens after you exit explore mode and approve a change proposal.

Does openspec-explore require the openspec CLI?

Yes, the Skill requires the openspec CLI installed on the machine. It uses commands like `openspec list`, `openspec status`, `openspec new change`, and `openspec instructions` to read context and scaffold change artifacts.

Can explore mode modify my existing OpenSpec change artifacts?

It can update proposals, designs, specs, and tasks when you approve capturing a decision, but it offers first and never auto-captures. It reads existing artifacts via `openspec status` to ground the discussion.

When should I not use explore mode?

Avoid explore mode when you already know exactly what to build and just want implementation. Explore mode deliberately refuses to write code, so use it only for thinking, investigation, and requirements clarification.