openspec-explore

Reason through problems and map code structures with ASCII diagrams.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill openspec-explore-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/jrmatherly/spacebot/tree/main/.windsurf/skills/openspec-explore
Command: npx skills add https://github.com/jrmatherly/spacebot --skill openspec-explore-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thinking partner in explore mode to ideate, reason, and clarify requirements without writing code, helping teams navigate ambiguous problems.

Core Features & Use Cases

  • Think deeply and visualize freely to surface ideas, constraints, and assumptions.
  • Ask clarifying questions to uncover hidden requirements and edge cases.
  • Ground discussions in the codebase with ASCII diagrams and concept maps.
  • Escalate to artifacts when needed by proposing designs or exploration notes.

Quick Start

Enter explore mode and start thinking deeply while visualizing potential directions.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I brainstorm solutions and clarify requirements without writing code?

You can use an ideation partner to brainstorm solutions and clarify requirements without writing code, helping you reason through ambiguous problems by surfacing constraints and hidden edge cases.

Can I generate ASCII diagrams to visualize code structures during exploration?

Yes, you can generate ASCII diagrams and concept maps to visualize code structures and map out potential directions while grounding your exploration in the codebase.

What is the best way to map out ambiguous problems and surface hidden assumptions?

The best way to map out ambiguous problems is to enter an exploration mode that asks clarifying questions, visualizes ideas freely, and surfaces constraints and assumptions.

Does this tool generate actual code implementations or only design specifications?

This tool explicitly excludes coding or implementation tasks, focusing solely on generating proposals, designs, exploration notes, and specifications as artifacts when requested.

When should I not use an explore mode for problem-solving?

You should not use an explore mode when you need to write or execute code, as it is strictly designed for thinking deeply, visualizing ideas, and reasoning through options without implementation.