openspec-explore

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

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-explore-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-explore-marcel-carrillo

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 explore ideas, investigate the codebase, compare options, and clarify requirements without writing any application code. ## Core Features & Use Cases - Exploration Stance: Acts as a curious thinking partner that asks open questions, challenges assumptions, and surfaces multiple directions instead of following a fixed script. - Codebase Investigation: Reads files, maps existing architecture, finds integration points, and visualizes findings with ASCII diagrams, state machines, and comparison tables. - OpenSpec Integration: Checks active changes via the openspec CLI, reads existing proposals, designs, and specs, and offers to capture decisions into the right artifacts (proposal.md, design.md, specs, tasks.md). - Use Case: Before building a new authentication system, enter explore mode to diagram the current auth flow, compare OAuth providers, surface risks, and then capture the agreed design decisions into an OpenSpec change proposal. ## Quick Start Ask the AI to enter explore mode and think through your idea or problem, for example by saying: explore how we should add real-time collaboration to the product 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?▼

Enter explore mode and describe your idea or problem in natural language. The skill investigates the codebase, draws diagrams, compares options, and offers to capture decisions into OpenSpec artifacts like proposals or design documents when you are ready.

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

Explore mode is for thinking only: it never writes application code and has no required outputs. Creating a change proposal is the formal next step that defines scope, specs, and tasks once exploration has crystallized into a decision.

Does openspec-explore require the openspec CLI?▼

Yes, the skill requires the openspec CLI to check active changes with openspec list and to read change status and artifact paths. Without it, exploration still works but OpenSpec context awareness is unavailable.

Can explore mode modify my existing specs or design documents?▼

It can update OpenSpec artifacts such as specs, design.md, proposal.md, and tasks.md, but only after offering to do so and receiving your confirmation. It never auto-captures decisions or writes application code.

When should I not use explore mode?▼

Avoid explore mode when you already know exactly what to build and just want implementation. In that case, create a change proposal directly and proceed with tasks, since explore mode deliberately avoids writing code.