openspec-explore

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

7|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/sap-tutorials/tutorials-ims --skill openspec-explore-sap-tutorials
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/sap-tutorials/tutorials-ims/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/sap-tutorials/tutorials-ims --skill openspec-explore-sap-tutorials

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 investigate the codebase, compare approaches, and crystallize decisions before committing to a change. ## Core Features & Use Cases - Codebase-grounded exploration: Reads existing architecture, integration points, and patterns to ground discussions in reality rather than theory. - Visual thinking: Produces ASCII diagrams, state machines, comparison tables, and architecture sketches to clarify complex problems. - OpenSpec integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions into specs, design.md, tasks.md, or proposal.md. - Use Case: Before adding real-time collaboration to your app, enter explore mode to map the collaboration spectrum (presence, cursors, CRDTs), weigh tradeoffs, and then formalize the chosen direction as an OpenSpec change proposal. ## Quick Start Ask the assistant to enter explore mode to think through your idea or investigate a 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 an idea before writing code with OpenSpec?▼

Invoke explore mode and describe your idea or problem. The assistant investigates the codebase, draws diagrams, compares options, and only creates OpenSpec artifacts like proposals or specs when you explicitly ask.

What is the difference between explore mode and creating a change proposal?▼

Explore mode is for thinking: reading code, asking questions, and visualizing tradeoffs without implementing anything. A change proposal formalizes the outcome into OpenSpec artifacts once the direction is clear.

Does openspec-explore require the openspec CLI?▼

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

Can explore mode write or modify application code?▼

No. Explore mode explicitly forbids writing code or implementing features. It may only read files, search the codebase, and create or update OpenSpec artifacts such as proposals, designs, specs, and tasks when requested.

When should I not use explore mode?▼

Avoid it when you already know exactly what to build and just want implementation. Explore mode adds thinking time, so well-defined tasks should go straight to a change proposal and implementation workflow.