openspec-explore

Explore problems, codebases, and options without implementing solutions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-explore-dvazquezd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/dvazquezd/openspec-governance/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-explore-dvazquezd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users think through problems, explore ideas, and understand complex situations before committing to implementation or code changes.

Core Features & Use Cases

  • Deep Thinking Partner: Acts as a sounding board for ideas, challenges assumptions, and surfaces risks.
  • Codebase Investigation: Maps architecture, finds integration points, and identifies existing patterns.
  • Option Comparison: Brainstorms approaches, sketches tradeoffs, and visualizes complex systems.
  • Use Case: Before starting a new feature, use this Skill to explore different architectural approaches, visualize potential data flows, and identify potential risks, ensuring a well-considered plan.

Quick Start

Use the openspec-explore skill to think through the problem of 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 explore architectural approaches before implementing a new feature?

To explore architectural approaches before implementing a new feature, use this Skill to brainstorm options, sketch tradeoffs, and visualize potential data flows. It acts as a deep thinking partner to challenge assumptions and surface risks without writing any code.

What is the best way to map an existing codebase and identify integration points?

The best way to map an existing codebase and identify integration points is to use this Skill for code investigation. It analyzes your codebase to surface existing patterns and visualize the system architecture through natural language interaction.

Can I compare different design options and visualize system tradeoffs without writing code?

Yes, you can compare different design options and visualize system tradeoffs without writing code. This Skill facilitates option comparison by sketching tradeoffs and visualizing complex systems to help you clarify requirements before committing to implementation.

Do I need external dependencies to analyze and clarify software requirements?

No, you do not need external dependencies to analyze and clarify software requirements. This Skill requires no external dependencies beyond the core agent environment to investigate code and facilitate deep problem exploration.

How do I surface potential risks when planning complex software systems?

To surface potential risks when planning complex software systems, use this Skill to act as a sounding board for your ideas. It challenges assumptions and highlights risks through natural language interaction and codebase investigation.

When should I use a problem exploration skill instead of directly implementing solutions?

You should use a problem exploration skill instead of directly implementing solutions when you need to think through complex situations, understand integration points, or compare approaches. It ensures a well-considered plan by clarifying requirements before any code changes occur.