openspec-explore

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-explore-kevmendesdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/KevMendesDev/mercadinho-sao-francisco/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-explore-kevmendesdev

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 structured thinking partner that investigates the codebase, challenges assumptions, and captures decisions as OpenSpec change artifacts without writing implementation code. ## Core Features & Use Cases - Guided Discovery: Asks focused questions, follows dependencies between decisions, and grounds discussion in the actual codebase rather than theory. - ASCII Visualization: Draws architecture diagrams, state machines, and comparison tables in plain ASCII to clarify complex problems. - OpenSpec Integration: Reads existing change status via the openspec CLI, scaffolds new changes with openspec new change, and captures decisions into proposals, designs, specs, and tasks. - Use Case: A developer is unsure whether to use SQLite or Postgres for a CLI tool. The Skill inspects the project, maps constraints, compares options in a table, and once a decision is made, offers to capture it in a design.md artifact. ## Quick Start Ask the assistant to enter explore mode and think through whether a planned feature should be built, before writing any code.

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 feature idea before writing code?▼

Enter explore mode and describe your idea or problem. The assistant investigates the codebase, asks focused questions, draws ASCII diagrams, and compares options. Nothing is implemented until you exit explore mode and approve a change proposal.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking stance for clarifying requirements and investigating problems before implementation. It can read files, run read-only openspec commands, and create or update OpenSpec change artifacts like proposals and designs, but never writes production code.

Does openspec-explore require the openspec CLI?▼

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

Can explore mode write code or implement features?▼

No, explore mode never writes implementation code or edits workflow configuration. It only creates or updates OpenSpec change artifacts such as proposal.md, design.md, specs, and tasks.md, and only after explicit user confirmation of the scope.

When should I not use explore mode?▼

Avoid explore mode when the task is already fully specified and you simply need implementation. In that case, create or follow an existing change proposal directly, since explore mode is designed for open-ended thinking rather than execution.