openspec-explore

Explore ideas and requirements while investigating codebase architecture and capturing decisions in OpenSpec artifacts.

1|Updated Jan 11, 2026

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

Ready to run

npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-explore-clouddevcrusader

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/CloudDevCrusader/riddle-rush-mono-repo/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-explore-clouddevcrusader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users think through complex ideas, problems, or requirements by acting as a curious and adaptive thinking partner, grounding discussions in the codebase when necessary.

Core Features & Use Cases

Deep Thinking Partner: Engages in open-ended exploration, asking clarifying questions and challenging assumptions.
Codebase Investigation: Maps architecture, finds integration points, and identifies patterns within the project.
Option Comparison: Brainstorms approaches, sketches tradeoffs, and visualizes complex systems.
Use Case: A developer is unsure how to approach a new feature. They activate this Skill to explore the problem space, understand existing code, and brainstorm potential solutions before committing to an implementation path.

Quick Start

Use the openspec-explore skill to think through the user authentication system.

Frequently Asked Questions about openspec-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I explore a codebase to understand integration points before starting a new feature?▼

To explore a codebase for new features, this Skill maps architecture and finds integration points by acting as a visual thinking partner. It investigates existing patterns and clarifies requirements without writing implementation code.

What is the best way to brainstorm approaches and compare design options for a software project?▼

The best way to compare design options is using a thinking partner that sketches tradeoffs and visualizes complex systems. This Skill facilitates open-ended exploration, challenging assumptions to surface risks before committing to a path.

Can I use this to clarify requirements and map system architecture for a proposal?▼

Yes, you can use this Skill to clarify requirements and map architecture for proposals. It integrates with the OpenSpec system to capture decisions in artifacts, grounding your design proposals in the actual codebase.

How do I investigate existing code patterns when unsure how to approach a problem?▼

To investigate existing code patterns when unsure how to approach a problem, this Skill acts as a curious thinking partner. It surfaces risks, maps architecture, and asks clarifying questions to help you understand the project.

Does this thinking partner tool actually write code implementation during exploration?▼

No, this thinking partner tool does not write code implementation during exploration. It focuses strictly on investigating the codebase, mapping options, and clarifying requirements to help you think through problems deeply.