openspec-explore

Explores ideas and investigates codebases in a read-only thinking mode using OpenSpec and CodeGraph context.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-explore-te-quanbzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/openspec-explore
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-explore-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need to think through a problem, investigate architecture, or clarify requirements before writing code, jumping straight into implementation leads to rework. This Skill provides a dedicated explore mode where the AI acts as a thinking partner that investigates your codebase and helps ideas crystallize without writing any application code. ## Core Features & Use Cases - Codebase-grounded exploration: Runs openspec list and codegraph explore to ground discussions in your actual change proposals, symbols, call paths, and architecture. - Visual thinking: Produces ASCII diagrams, comparison tables, and state machines to clarify problems, options, and tradeoffs. - Insight capture into OpenSpec artifacts: Offers to record decisions, requirements, and scope changes into proposal.md, design.md, specs, and tasks.md when a change exists. - Use Case: You are mid-implementation on an auth change and realize OAuth is more complex than expected. Enter explore mode to trace the current flow, compare integration options, and update design.md with the new decision before resuming tasks. ## Quick Start Ask the AI to enter explore mode and help you think through a problem, for example by saying: explore how we should add real-time collaboration to this project.

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 codebase before starting an implementation?

Enter explore mode and state your topic. The skill runs openspec list to check active changes and codegraph explore to surface relevant symbols, call paths, and architecture, then discusses findings with diagrams and questions.

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

Explore mode is strictly read-only for application code: it investigates, diagrams, and discusses but never writes features. It may create or update OpenSpec artifacts like proposals, designs, and specs when you ask to capture decisions.

Does openspec-explore require the OpenSpec CLI?

Yes, the skill requires the openspec CLI to list changes, read change status, and capture artifacts. CodeGraph is optional but recommended for grounding discussions in real code symbols and call paths.

Can explore mode update my design or spec documents?

Yes, when a decision or new requirement emerges, it offers to record it in the appropriate artifact such as design.md, proposal.md, specs, or tasks.md. It only captures after you confirm and never auto-captures.

When should I not use explore mode?

Avoid explore mode when you already know what to build and want code written. In that case, exit explore mode and create a change proposal so implementation tasks can proceed through the normal OpenSpec workflow.