openspec-explore

Explore codebases and clarify requirements without implementing changes.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/arestivo/qoodle --skill openspec-explore-arestivo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/arestivo/qoodle/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/arestivo/qoodle --skill openspec-explore-arestivo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec explore mode provides a guided thinking space that helps teams think through ideas, investigate problems, and clarify requirements without making changes or writing production code.

Core Features & Use Cases

  • Non-implementing thinking partner: read files, inspect the codebase, and discuss options without executing changes.
  • Visual reasoning: produce ASCII diagrams and structured notes to surface risks, assumptions, and multiple directions.
  • OpenSpec artifact-ready: you can propose designs, proposals, or tasks if the user asks, without committing to implementation.

Quick Start

Activate explore mode with /opsx:explore to start a collaborative thinking session and guide the user through questions, patterns, and potential next steps.

Frequently Asked Questions about openspec-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore ideas and clarify requirements before writing any code?

To explore ideas and clarify requirements before writing code, use a collaborative thinking session to read files, search the codebase, map options, and visualize scenarios without executing changes.

What is the best way to investigate problems and capture design proposals without modifying the codebase?

Investigating problems and capturing proposals without modifying the codebase involves using a non-implementing thinking partner that surfaces risks and assumptions through structured notes and ASCII diagrams.

Can I map out project requirements and visualize scenarios without executing code?

Yes, you can map out requirements and visualize scenarios without executing code by using explore mode to discuss multiple directions, generate ASCII diagrams, and capture concerns as optional artifacts.

How do I start a collaborative thinking session for requirement elicitation?

Start a collaborative thinking session for requirement elicitation by activating explore mode, which guides you through questions, patterns, and potential next steps to surface assumptions.

Does explore mode work for early discovery and design exploration in an existing codebase?

Yes, explore mode works for early discovery and design exploration in an existing codebase by letting you inspect files, discuss options, and propose designs while avoiding automated changes.

When should I not use a non-implementing thinking partner for my project?

You should not use a non-implementing thinking partner when you need automated changes, code execution, or mandatory outputs, as it focuses purely on thinking through ideas and clarifying requirements.