openspec-explore

Explores ideas, investigates codebases, and clarifies requirements through OpenSpec-guided thinking sessions.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill openspec-explore-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Wizarck/nexandro/tree/main/skills/openspec-explore
Command: npx skills add https://github.com/Wizarck/nexandro --skill openspec-explore-wizarck

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 helps you explore ideas, investigate your codebase, and clarify requirements before or during a change—without writing any code. ## Core Features & Use Cases - Explore Mode Stance: Acts as a curious, adaptive thinking partner that asks natural questions, challenges assumptions, and surfaces multiple directions instead of following a rigid script. - Codebase Investigation: Reads files, maps architecture, finds integration points, and visualizes systems with ASCII diagrams to ground discussions in reality. - OpenSpec Integration: Detects active changes via the openspec CLI, reads existing proposals/designs/specs, and offers to capture decisions in the right artifacts (proposal.md, design.md, tasks.md, specs). - Use Case: You are mid-implementation on an auth change and realize OAuth is more complex than expected. Enter explore mode to trace the flow, diagram the tangles, compare options, and update the design artifact before continuing. ## Quick Start Ask the AI to enter explore mode to think through a vague feature idea or investigate a problem in your codebase 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, however vague. The skill acts as a thinking partner: it asks clarifying questions, sketches ASCII diagrams of the problem space, and compares approaches. When thinking crystallizes, it can offer to create an OpenSpec change proposal.

What is OpenSpec explore mode used for?

Explore mode is for thinking, not implementing. It helps you investigate the codebase, map architecture, compare options, and clarify requirements. It may create or update OpenSpec artifacts like proposals and designs, but never writes application code.

Can explore mode read my existing OpenSpec change proposals?

Yes. It runs openspec list --json to detect active changes, then reads proposal.md, design.md, tasks.md, and spec files for context. It references these artifacts naturally and offers to capture new decisions in the appropriate file.

Does explore mode implement features or write code?

No. Explore mode explicitly never writes code or implements features. If you ask for implementation, it reminds you to exit explore mode and create a change proposal first. Creating OpenSpec artifacts is allowed since that captures thinking.

What are the limitations of using explore mode for planning?

Explore mode has no fixed workflow or guaranteed outputs, so it does not replace formal planning by itself. It requires the openspec CLI for change awareness, and its value depends on the conversation—sometimes the thinking itself is the only deliverable.