openspec-explore

Frame problems and surface design options with ASCII diagrams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Guided thinking: provides a collaborative space to think aloud, map questions, and visualize options using ASCII diagrams.
  • Non-code exploration: read code or docs, surface design choices, and propose thoughtful questions without implementing changes.
  • Use Case: when planning a feature, use explore mode to surface requirements and tradeoffs before drafting specs or implementation.

Quick Start

Ask the assistant to start exploration and outline questions, options, and diagrams.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore design options and frame problems before implementing code?

To explore design options and frame problems, you can use a guided thinking partner to map questions, surface design choices, and visualize tradeoffs using ASCII diagrams before drafting implementation specs.

Can I brainstorm requirements and investigate problems without modifying the codebase?

Yes, you can brainstorm requirements without modifying the codebase by reading existing code or documents to surface thoughtful questions and design choices without implementing changes.

What is the best way to visualize tradeoffs during early feature planning?

The best way to visualize tradeoffs during early feature planning is by using exploratory visualization tools that generate ASCII diagrams to map out questions and options.

Does this exploratory thinking approach work for both codebases and documentation?

Yes, this exploratory thinking approach works across both codebases and documents, allowing you to investigate problems and clarify requirements by analyzing existing technical information.

How do I start an ideation session to clarify feature requirements?

You start an ideation session by asking the assistant to enter exploration mode, which then collaboratively outlines questions, options, and diagrams to clarify your feature requirements.