Is explore mode suitable for debugging?

Yes, it is excellent for the 'investigation' phase of debugging where you need to understand the root cause and trace data flows without changing code yet.

How does it help with existing codebases?

It can search and read your files to map existing architecture, find patterns, and identify hidden complexities before you commit to a change.

Does this skill require external tools?

Yes, this skill requires the openspec CLI to be installed and configured in your environment to manage system context and artifacts.

What kind of artifacts can this skill create?

It can create and update OpenSpec-compliant artifacts including proposals, design documents, specifications, and task lists to capture your thinking.

Can I write application code while in explore mode?

No, explore mode is strictly for thinking and investigation. To write code, you should exit explore mode and start a change using commands like /opsx:new.

OpenSpec Explore Mode

Name: OpenSpec Explore Mode
Author: durandom

bydurandom

0•

生産性とワークフロー

Transforms Claude into a dedicated thinking partner for architectural exploration, problem-solving, and requirement clarification.

OpenSpec Explore Mode provides a non-prescriptive environment for developers to navigate complex codebases and brainstorm architectural changes without the risk of accidental implementation. By enforcing a strict boundary between thinking and coding, it allows Claude to focus entirely on surfacing risks, mapping existing patterns, and visualizing system flows through detailed ASCII diagrams. It integrates with the OpenSpec CLI to help document decisions in proposals or design specs, making it the essential tool for the discovery and planning phases of the software development lifecycle.

主な機能

01Deep architectural investigation and codebase mapping to ground discussions in reality

02Seamless integration with OpenSpec artifacts like proposals, designs, and task lists

03Strict 'thinking-only' guardrails that prevent code modification during discovery phases

04Liberal use of ASCII diagrams for visualizing state machines, data flows, and system sketches

05Comprehensive comparison of technical options with trade-off analysis and risk identification

060 GitHub stars

ユースケース

01Brainstorming and comparing multiple architectural paths for a specific problem space

02Navigating and mapping complex, unfamiliar codebases to identify integration points

03Refining vague feature ideas into concrete technical requirements before implementation

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add durandom/layton openspec-explore

For use in Claude.ai and ChatGPT

Download Skill