Verified:GitHub

openspec-explore

Explore software design ideas and clarify requirements through guided questioning.

1|Updated Mar 7, 2026

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

Ready to run

npx skills add https://github.com/thalesraymond/release-gamification --skill openspec-explore-thalesraymond

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/thalesraymond/release-gamification/tree/main/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/thalesraymond/release-gamification --skill openspec-explore-thalesraymond

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 without the pressure of immediate implementation.

Core Features & Use Cases

Facilitates deep thinking: Encourages curiosity, open-ended exploration, and visualization of complex topics.
Codebase investigation: Allows users to explore the actual codebase, map architecture, and identify integration points.
Option comparison: Helps brainstorm approaches, sketch tradeoffs, and visualize options.
Use Case: A user wants to understand the potential impact of a new feature on the existing authentication system. This Skill can help them visualize the current auth flow, identify potential conflicts, and explore alternative designs.

Quick Start

Use the openspec-explore skill to think through the implications of adding a new feature.

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 ideas before writing code?▼

To clarify requirements and explore ideas, you can use this Skill as a thinking partner that asks clarifying questions, challenges assumptions, and visualizes concepts with ASCII diagrams to help you investigate problems without immediate implementation pressure.

What is the best way to investigate a codebase and map architecture for new features?▼

The best way to investigate a codebase is to explore the actual code, map the architecture, and identify integration points. This Skill helps you visualize current flows, identify potential conflicts, and explore alternative designs for new features.

Can I compare design options and sketch tradeoffs for software architecture?▼

Yes, you can compare design options and sketch tradeoffs for software architecture. This Skill helps brainstorm approaches, visualize options, and facilitates deep thinking to evaluate the impact of new features on existing systems.

Does this tool generate code or focus on decision-making and exploration?▼

This tool focuses on exploration and decision-making rather than direct code implementation. It acts as a thinking partner to help you investigate problems, clarify requirements, and reference existing code and artifacts.

How do I visualize the impact of a new feature on an existing authentication system?▼

To visualize the impact of a new feature on an authentication system, this Skill helps you map the current auth flow, identify potential conflicts, and explore alternative designs using ASCII diagrams and deep thinking exploration.

When should I use a thinking partner for codebase investigation instead of coding directly?▼

You should use a thinking partner for codebase investigation when you need to understand complex topics, clarify requirements, or evaluate design options before committing to implementation. It encourages curiosity and open-ended exploration of problems.