openspec-explore

Explore codebases and surface questions to shape OpenSpec requirements.

Updated Feb 4, 2026

Search Tags:#codebase #requirements #visualization #open-spec #explore #design-thinking #thinking-partner

Ready to run

npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-explore-sqdr2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-explore
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-explore-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to serve as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when you want to think through something before or during a change.

Core Features & Use Cases

Guided thinking partner for open-ended discussions.
Reading and reasoning about codebases or designs without implementing changes.
Surface questions, diagrams, and OpenSpec artifacts to capture exploration.

Quick Start

Describe your goal and I will start an open-ended exploration to surface questions and possible directions.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore and clarify requirements before making codebase changes?▼

A thinking partner helps you explore ideas and clarify requirements by reading your codebase, reasoning about designs, and surfacing questions to shape potential OpenSpec artifacts without implementing changes.

What is the best way to visualize a problem space and potential exploration paths?▼

Visualizing a problem space involves articulating goals, reading relevant codebase structures, and surfacing questions or diagrams to capture the design thinking process and outline potential exploration paths.

Can I use this to read and reason about my codebase without modifying the code?▼

Yes, you can read and reason about codebases or designs without implementing changes. The focus remains on open-ended discussion to investigate problems and capture requirements rather than modifying code.

How do I start an open-ended exploration to surface questions and possible directions?▼

Describe your goal to start an open-ended exploration. The thinking partner will then analyze the problem space, read relevant codebase sections, and surface questions along with potential OpenSpec artifacts to guide direction.

When should I use a thinking partner instead of directly implementing changes?▼

Use a thinking partner when you need to think through something before or during a change. It helps investigate problems, clarify requirements, and surface OpenSpec artifacts rather than immediately writing code.