openspec-explore

Name: openspec-explore
Availability: InStock
Author: runecalico-ai

Explore codebases and compare options using ASCII diagrams.

Updated Jan 9, 2026

Search Tags:#design thinking #problem solving #exploration #codebase investigation #thinking partner #requirements clarification

Ready to run

npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-explore-runecalico-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/runecalico-ai/second_edition_spellbook/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-explore-runecalico-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a thinking partner to help users explore ideas, investigate problems, and clarify requirements within a codebase or project context, without directly implementing changes.

Core Features & Use Cases

Deep Thinking Partner: Engages in curious, adaptive, and visual exploration of user-provided topics.
Codebase Investigation: Maps architecture, finds integration points, and surfaces complexity within the project.
Option Comparison: Brainstorms approaches, sketches tradeoffs, and visualizes options using ASCII diagrams.
Use Case: A user wants to understand the implications of adding a new feature. This Skill helps them think through the problem space, explore relevant code, and compare potential solutions before any implementation begins.

Quick Start

Start exploring ideas by describing what you want to think through.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore ideas and investigate problems in a codebase before implementation?▼

To explore ideas and investigate problems in a codebase, you can use a thinking partner Skill to map architecture, find integration points, and surface complexity through natural language interaction without directly implementing changes.

What is the best way to clarify software requirements and compare potential solutions?▼

The best way to clarify software requirements is to brainstorm approaches and sketch tradeoffs visually using ASCII diagrams, which helps you compare potential solutions and understand the problem space before committing to an implementation.

Can I use this thinking partner to visualize codebase architecture and integration points?▼

Yes, you can use this thinking partner to visualize codebase architecture and integration points, as it supports mapping architecture and surfacing complexity through natural language interaction and ASCII diagrams.

How do I think through the implications of adding a new feature to my project?▼

To think through the implications of adding a new feature, you describe what you want to explore, and the Skill facilitates a deep thinking process to investigate relevant code, clarify requirements, and compare options within your software development context.

Does this codebase investigation tool directly modify my project files?▼

No, this codebase investigation tool operates as a non-implementing partner, meaning it focuses entirely on discovery, understanding, and exploration without directly implementing any changes to your project files.

When should I not use an exploration partner for software development?▼

You should not use an exploration partner when you need direct code implementation or automated file modifications, as this Skill strictly focuses on discovery, requirements clarification, and visualizing options rather than writing or applying code changes.