openspec-explore

Guide analysis of ideas and requirements through questioning and ASCII diagrams.

68|7|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-explore-drakulavich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/drakulavich/kesha-voice-kit/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-explore-drakulavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explore mode provides a thinking-partner experience that helps users think through ideas, problems, and requirements without implementing changes.

Core Features & Use Cases

  • Open-ended questioning to surface assumptions and multiple directions.
  • ASCII-diagram visualization to map ideas, dependencies, and workflows.
  • Risk and unknowns surfacing to surface potential gaps and decisions.

Quick Start

Ask OpenSpec to enter explore mode and begin thinking through your idea.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
What is a thinking partner for problem framing and how does it help with requirements gathering?

A thinking partner for problem framing is an interactive process that helps you think through ideas and requirements by surfacing assumptions, asking open-ended questions, and identifying risks without implementing actual changes.

Can I use ASCII diagram visualization to map dependencies during requirement gathering?

Yes, you can use ASCII diagram visualization during requirement gathering to map ideas, workflows, and dependencies, which helps clarify complex problem spaces and alternative directions.

What is the best way to surface unknowns and risks during change discussions?

The best way to surface unknowns during change discussions is to use a guided analysis process that asks open-ended questions, highlights potential gaps, and maps decisions without committing to implementation.

Does this problem-framing approach work for open-ended ideation or only structured requirements?

This problem-framing approach works for open-ended ideation as well as structured requirements, using open-ended questioning to surface multiple directions and assumptions across various stages of analysis.

When should I not use an explore mode for thinking through ideas?

You should not use explore mode when you need to execute or implement changes; it is designed strictly for thinking through problems, visualizing workflows, and surfacing risks rather than modifying systems.