openspec-explore

Explore codebases and clarify requirements without implementing code changes.

Updated May 23, 2026

Search Tags:#architecture #debugging #requirements #exploration #openspec #decision-making

Ready to run

npx skills add https://github.com/devturco/thiago-dev-template --skill openspec-explore-devturco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/devturco/thiago-dev-template/tree/main/.github/skills/openspec-explore
Command: npx skills add https://github.com/devturco/thiago-dev-template --skill openspec-explore-devturco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you investigate requirements, clarify decisions, and explore the codebase without turning your exploration into unreviewed implementation work.

Core Features & Use Cases

Clarify requirements through exploration: Ask emergent questions, reframe assumptions, and map the problem space.
Investigate the actual codebase: Locate architecture patterns, integration points, and hidden complexity to ground your thinking.
Compare options and visualize tradeoffs: Use diagrams and structured comparisons to converge on a direction.
Optional OpenSpec capture: Create OpenSpec artifacts like proposals/designs/specs when the user asks, while staying in “thinking mode.”

Quick Start

Use openspec-explore when you need to explore how to approach a change, such as diagnosing an issue or clarifying scope, before any code is written.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore architecture and clarify requirements before writing code?▼

Requirement clarification and architecture exploration happen before implementation by investigating the codebase, reading files, and mapping the problem space while enforcing a strict no-implementation stance.

What is the best way to investigate codebase complexity for ambiguous feature discovery?▼

Codebase complexity investigation locates architecture patterns and integration points to ground your thinking, allowing safe research actions like reading files and using openspec CLI for context.

Can I compare decision tradeoffs and visualize options without making code changes?▼

Decision tradeoff comparison uses diagrams and structured comparisons to converge on a direction while staying in thinking mode, preventing unreviewed implementation work.

Does requirement exploration work with OpenSpec proposals and design specs?▼

OpenSpec integration allows creating proposal, design, and spec artifacts when explicitly requested, capturing exploration results without leaving the investigation phase.

When should I not use pre-implementation exploration for debugging?▼

Pre-implementation exploration is not suited for situations where code changes are ready to be made, as it enforces a strict no-implementation stance focused on problem-space investigation.