openspec-explore

Structures exploration of complex problems through guided, codebase-aware thinking sessions.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-explore-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-explore-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A thinking partner that helps users explore ideas, investigate problems, and clarify requirements without implementing changes.

Core Features & Use Cases

  • Guided exploration: A structured, open-ended thinking session that surfaces questions and options without enforcing actions.
  • Codebase-aware discussion: Read files and explore repository context to inform decisions without writing code.
  • Artifact generation: Propose designs, diagrams, and clarifications as OpenSpec artifacts while keeping the actual implementation out of scope.
  • Use cases: Refining requirements, decomposing problems, and aligning exploration goals with stakeholders.

Quick Start

Describe what you want to explore and I will begin a guided thinking session.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify requirements for a complex codebase without writing code?

Requirements clarification for a complex codebase is achieved by engaging in a guided exploration session that reads repository context and surfaces questions without implementing production code.

What is the best way to decompose a design problem alongside my existing project files?

Problem decomposition within existing project files is handled by acting as a thinking partner that explores repository context to inform decisions and breaks down the problem structure.

Can I generate design diagrams and artifacts while keeping implementation out of scope?

Generating design diagrams and artifacts while keeping implementation out of scope is supported by proposing reflective OpenSpec artifacts during open-ended inquiry without writing production code.

Does this thinking partner approach work for aligning exploration goals with stakeholders?

Aligning exploration goals with stakeholders is supported through structured, open-ended thinking sessions that surface options and refine requirements without enforcing immediate technical actions.

How do I start a guided exploration session for refining project requirements?

Starting a guided exploration session for refining project requirements requires you to describe what you want to explore, which initiates a structured thinking dialogue for ideation.

When should I not use an open-spec exploration session for my codebase?

An open-spec exploration session should not be used when you need to directly implement changes or write production code, as it strictly focuses on non-implementational reasoning and reflective artifact generation.