openspec-explore

Explore ideas and clarify requirements with ASCII diagrams and OpenSpec guardrails.

43|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/liyown/XHSSpec --skill openspec-explore-liyown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/liyown/XHSSpec/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/liyown/XHSSpec --skill openspec-explore-liyown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to think deeply about ideas, investigate problems, and clarify requirements before moving to implementation.

Core Features & Use Cases

  • Acts as a non-judgmental thinking partner to surface questions, visualize options with ASCII diagrams, and surface risks.
  • Helps map the problem space, read codebases, and surface uncertainty to guide decision making.
  • Use during early design sessions or mid-workflow to align intents and prepare change proposals.

Quick Start

Begin exploring by asking clarifying questions and visualizing the problem space.

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 before starting codebase implementation?

A thinking partner helps clarify requirements by surfacing questions, mapping the problem space, and visualizing options. It guides decision-making during early design sessions to align intents before any implementation begins.

What is the best way to explore ideas and investigate problems in early design?

Exploring ideas works best with a non-judgmental thinking partner that visualizes options using ASCII diagrams and surfaces risks. It reads codebases and maps the problem space to highlight uncertainty for better decisions.

Can I generate design proposals without writing actual code?

You can generate design proposals without writing code by using an exploration mode that enforces strict no-coding guardrails. It focuses on clarifying requirements, surfacing risks, and preparing change proposals instead of implementation.

Does OpenSpec exploration mode support visualizing the problem space?

OpenSpec exploration supports visualizing the problem space by generating ASCII diagrams. It acts as a thinking partner to map options, surface risks, and highlight uncertainty during requirements refinement sessions.

When should I not use an exploratory thinking partner for problem-solving?

Avoid using an exploratory thinking partner when you need actual code implementation. It operates under strict no-coding guardrails and is designed exclusively for early design discussions, problem investigation, and requirements clarification.