openspec-explore

Explore problems and clarify requirements while capturing insights as OpenSpec proposals.

1|Updated Mar 7, 2026

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

Ready to run

npx skills add https://github.com/charlestang/UnaEditor --skill openspec-explore-charlestang

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users think through ideas, investigate problems, and clarify requirements in a flexible, exploratory manner before or during a change.

Core Features & Use Cases

Exploratory Thinking: Acts as a thinking partner to explore concepts and challenges.
Codebase Investigation: Can read files and investigate the codebase to understand context.
OpenSpec Integration: Naturally integrates with the OpenSpec system to capture insights.
Use Case: If you're unsure how to approach a new feature, you can use this Skill to brainstorm options, understand potential complexities, and map out the problem space.

Quick Start

Use the openspec-explore skill to think through the problem of adding real-time collaboration.

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 before implementing a new feature?▼

To clarify requirements, you can use exploratory thinking to investigate the codebase and map out the problem space before implementation. This Skill acts as a visual thinking partner to help brainstorm options and understand potential complexities without writing code.

What is the best way to investigate codebase implications for a proposed change?▼

Investigating codebase implications involves reading files and analyzing context to understand the impact of a proposed change. This Skill helps you explore the problem space and capture insights as formal proposals or specifications without implementing the solution.

Can I use exploratory thinking to compare architectural options without writing code?▼

Yes, exploratory thinking allows you to compare architectural options and map out the problem space without writing implementation code. This Skill serves as an adaptive thinking partner to help you evaluate concepts and challenges before committing to a specific design.

Does this requirements clarification process integrate with the OpenSpec system?▼

Yes, the requirements clarification process integrates with the OpenSpec system to capture insights. As you explore ideas and solve problems, the Skill records your decisions and findings as formal proposals, designs, or specifications within the system.

When should I not use this exploratory problem-solving approach?▼

You should not use exploratory problem-solving when you need to implement the solution, as this Skill explicitly focuses on investigation and clarification without writing code. It is designed for mapping out the problem space and capturing insights, not for generating the final implementation.