openspec-explore

Explores ideas, investigates codebases, and clarifies requirements through conversational analysis with ASCII diagrams.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-explore-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/openspec-explore
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-explore-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned designs. This Skill provides a structured thinking partner that helps you explore ideas, investigate existing code, compare options, and surface risks before committing to a change. ## Core Features & Use Cases - Exploratory Thinking Mode: Acts as a curious, non-prescriptive thinking partner that asks clarifying questions, challenges assumptions, and follows interesting threads without forcing a fixed workflow. - Codebase Investigation: Reads files, maps existing architecture, finds integration points, and grounds discussions in the actual code rather than theory. - ASCII Visualization: Renders system diagrams, state machines, data flows, and comparison tables to clarify complex thinking. - 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 building a real-time collaboration feature, use explore mode to map the spectrum from presence indicators to CRDT-based sync, compare tradeoffs, and crystallize the approach into a change proposal. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem, for example by describing a vague feature idea or a specific technical problem you want to investigate before implementing.

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 skill acts as a thinking partner that asks clarifying questions, sketches ASCII diagrams of the problem space, and helps you compare approaches before you commit to a change proposal.

What is OpenSpec explore mode used for?▼

Explore mode is a stance for thinking through problems, not a fixed workflow. It helps investigate codebases, surface risks, compare options, and clarify requirements, while explicitly prohibiting writing application code or implementing features.

Can explore mode create or update OpenSpec artifacts?▼

Yes, it can create proposals, designs, and specs when you ask, since capturing thinking is not implementing. It offers to record decisions in design.md, new requirements in specs, scope changes in proposal.md, and new work in tasks.md.

Does openspec-explore require the openspec CLI?▼

Yes, the skill declares compatibility with the openspec CLI. It runs openspec list --json at the start to detect active changes, their schemas, and status so it can reference existing artifacts naturally during the conversation.

When should I not use explore mode?▼

Do not use explore mode when you are ready to implement code, since it never writes application code by design. Exit explore mode and create a change proposal first, then move to an implementation-oriented workflow.