openspec-explore

Clarify ideas and requirements through questions and ASCII diagrams.

Updated Aug 23, 2026

Search Tags:#requirements #visualization #exploration #openspec #codebase-analysis #problem-framing

Ready to run

npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-explore-terry90918

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/terry90918/horse-blessing-2026/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-explore-terry90918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when you want to think through something before or during a change.

Core Features & Use Cases

Explore the problem space - Ask clarifying questions, challenge assumptions, reframe the problem.
Investigate the codebase - Map architecture, find integration points, surface patterns.
Surface risks and unknowns - Identify what could go wrong, surface gaps, suggest spikes.
Visualize - Use ASCII diagrams liberally to clarify concepts.
OpenSpec awareness - Check context and potential artifacts.

Quick Start

Describe your goal and I will explore the problem space with questions, diagrams, and options before taking action.

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 and explore a problem space before writing code?▼

To clarify requirements before coding, you can partner with an AI thinking tool that asks clarifying questions, challenges assumptions, and visualizes concepts with ASCII diagrams to help you reframe the problem and map out risks.

How does problem framing and codebase analysis work for architecture mapping?▼

Problem framing and codebase analysis work by investigating your existing code to map architecture, find integration points, and surface patterns, helping you understand the structure and identify potential risks before making changes.

What is the best way to investigate codebase risks and unknowns before a change?▼

The best way to investigate codebase risks is to use an exploration partner that identifies what could go wrong, surfaces gaps in your logic, and suggests spikes to validate assumptions before you commit to implementation.

Can I use ASCII diagrams to visualize architecture and design concepts during exploration?▼

Yes, you can use ASCII diagrams liberally during design exploration to clarify concepts, map out architecture, and visualize integration points without writing any actual implementation code.

Does this requirements exploration approach write or modify code directly?▼

No, this requirements exploration approach avoids implementing code entirely; it focuses solely on thinking through the problem, asking questions, and only suggests artifacts if you explicitly request them.

When do I need to explore options and surface risks for a new software design?▼

You need to explore options and surface risks when you want to think through a design or change beforehand, allowing an AI partner to assess your codebase, investigate problems, and clarify requirements before taking action.