openspec-explore

Explore codebases by surfacing questions, hypotheses, and investigation directions.

4|2|Updated Aug 27, 2025

Search Tags:#ideation #requirements #problem-solving #visualization #exploration #OpenSpec #thinking-partner

Ready to run

npx skills add https://github.com/finger-gun/sisu --skill openspec-explore-finger-gun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-explore
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-explore-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.

IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first (e.g., start a change with /opsx:new or /opsx:ff). You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.

Core Features & Use Cases

Explore the problem space with clarifying questions, multiple angles, and surface risks.
Surface interesting threads, diagrams, and dependencies to guide decision-making.
Surface risks and unknowns, suggesting spikes or investigations.

Quick Start

Begin by introducing a topic to explore and asking open-ended questions to surface assumptions and uncertainties.

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 refine problem requirements without writing any code?▼

To explore and refine requirements without writing code, use a guided thinking partner that surfaces clarifying questions, hypotheses, and potential directions. This approach focuses on problem framing and ideation across codebases, strictly avoiding implementation while you visualize freely.

What is the best way to frame a complex problem space and surface unknowns during ideation?▼

The best way to frame a complex problem space during ideation is by using a conversational exploration tool that surfaces risks, unknowns, and multiple angles. This method helps visualize dependencies and suggests investigations to guide decision-making without prescribing implementations.

Can I use this exploration mode to create OpenSpec proposals and design artifacts?▼

Yes, you can use exploration mode to create OpenSpec proposals, designs, and specs. Capturing your thinking in these artifacts is permitted because it represents refining requirements and problem framing, whereas writing actual code or implementing features is strictly prohibited.

Does guided problem exploration help with visualizing dependencies and suggesting investigations?▼

Guided problem exploration helps with visualizing dependencies by surfacing interesting threads and diagrams to guide decision-making. It also identifies risks and unknowns, suggesting specific spikes or investigations to thoroughly examine the codebase and OpenSpec contexts.

What are the limitations of using a thinking partner for requirement refinement?▼

The main limitation of using a thinking partner for requirement refinement is that it cannot write code or implement features. If you request implementation, you must exit explore mode first and initiate a change using commands like /opsx:new or /opsx:ff.