openspec-explore

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-explore-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-explore-jhonma82

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 exploration mode where you can think through ideas, investigate the codebase, compare options, and clarify requirements before committing to a change. ## Core Features & Use Cases - Exploration Mode: Acts as a thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without writing any implementation code. - Codebase Investigation: Maps existing architecture, finds integration points, and grounds discussions in the actual code using ASCII diagrams and visualizations. - OpenSpec Integration: Captures crystallized decisions as OpenSpec artifacts (proposals, designs, specs, tasks) via the openspec CLI, with support for registered standalone stores. - Use Case: Before adding real-time collaboration to your app, use explore mode to compare approaches (presence indicators vs CRDTs), map the current architecture, and then scaffold a change proposal once the direction is clear. ## Quick Start Ask the assistant to enter explore mode and think through whether Postgres or SQLite 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 a feature idea before writing code?▼

Enter explore mode and describe your idea in natural language. The assistant investigates the codebase, draws ASCII diagrams of options and tradeoffs, and asks clarifying questions without writing any implementation code.

How to create an OpenSpec change proposal from an exploration?▼

Once the exploration crystallizes, ask to capture it as a change. The assistant runs openspec new change to scaffold the change, then follows status and instructions commands to create the requested artifacts in dependency order.

Does openspec-explore write application code?▼

No, explore mode never writes implementation code. It only reads files, searches the codebase, and optionally creates OpenSpec artifacts like proposals, designs, and specs when explicitly requested.

What is the openspec CLI requirement for this skill?▼

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.

When should I use explore mode instead of starting a change directly?▼

Use explore mode when the problem is vague, multiple approaches exist, or assumptions need validation. Start a change directly only when requirements and design direction are already clear.