openspec-explore

Explore ideas and investigate codebase problems through natural language interaction.

1|1|Updated Feb 28, 2026

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

Ready to run

npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-explore-kevintsengtw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/kevintsengtw/dotnet-testing-agent-orchestration/tree/main/.github/skills/openspec-explore
Command: npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-explore-kevintsengtw

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 immediately jumping into implementation.

Core Features & Use Cases

Facilitates deep thinking: Encourages curiosity, open-ended questions, and visualization.
Codebase investigation: Helps users map architecture, find integration points, and surface complexity.
Option comparison: Brainstorms approaches, builds comparison tables, and sketches tradeoffs.
Use Case: A developer is unsure how to approach a new feature. They activate this Skill to discuss potential architectures, explore existing code patterns, and visualize different implementation paths before writing any code.

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 brainstorm architectures and investigate a codebase before starting implementation?▼

To explore ideas and investigate a codebase before implementation, use an AI thinking partner to map architecture, find integration points, and discuss potential approaches through natural language interaction without writing code immediately.

What is the best way to clarify requirements and compare design options for a new feature?▼

The best way to clarify requirements and compare options is to facilitate deep thinking through open-ended questions, brainstorm approaches, build comparison tables, and sketch tradeoffs visually to capture insights before development.

Can I use design thinking to map existing code patterns and surface complexity?▼

Yes, applying design thinking principles helps you map existing code patterns, surface complexity, and find integration points by encouraging curiosity and visualizing different implementation paths within your codebase.

How do I explore ideas for adding real-time collaboration to my project?▼

To explore ideas for adding real-time collaboration, activate a thinking partner to discuss potential architectures, investigate existing code patterns, and visualize different implementation paths to clarify requirements.

Does this codebase investigation approach require any specific dependencies?▼

No, this codebase investigation and requirements clarification approach requires no specific dependencies, allowing you to explore ideas and capture decisions using natural language interaction directly.

When should I avoid jumping into implementation and focus on problem exploration?▼

You should focus on problem exploration instead of implementation when you are unsure how to approach a new feature, need to clarify requirements, or want to compare architectural tradeoffs before committing to code.