openspec-explore

Guide requirement clarification and codebase investigation without enabling implementation.

Updated May 21, 2026

Search Tags:#investigation #requirements #trade-off analysis #architecture exploration #openSpec #problem clarification

Ready to run

npx skills add https://github.com/yeongjet/easytickets2 --skill openspec-explore-yeongjet

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you clarify requirements, investigate ideas, and reduce uncertainty by guiding deep exploration instead of jumping straight to implementation.

Core Features & Use Cases

Exploration-first guidance: Acts as a thinking partner for questioning assumptions and reshaping unclear problems.
Safe codebase investigation: Encourages reading files, searching code, and mapping architecture to ground your discussion in reality.
Decision support via comparison: Helps you brainstorm options, surface trade-offs, and recommend directions without committing code.
Use Case: When you suspect “the authentication system is a mess,” use this mode to explore the current flow, identify confusing parts, and decide what to investigate next.

Quick Start

Use openspec-explore when you want to think through a change before implementing it, for example by asking: “What are the key uncertainties in our current design, and what should we investigate first?”

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 and investigate architecture before changing code?▼

To clarify requirements and investigate architecture before changing code, use an exploration-first approach that questions assumptions and maps the existing codebase. This guides deep thinking to reduce uncertainty without enabling implementation.

What is the best way to analyze trade-offs between different solution directions?▼

Analyzing trade-offs between solution directions involves brainstorming available options and surfacing their comparative strengths. This decision support process helps recommend directions while preventing premature commitment to code changes.

How do I troubleshoot confusing parts of an existing codebase without implementing features?▼

Troubleshooting an existing codebase without implementing features requires reading files, searching code, and mapping architecture. This grounds your investigation in reality and enforces constraints to prevent coding during the analysis.

Can I use pre-change analysis to question assumptions and reshape unclear problems?▼

Yes, you can use pre-change analysis to question assumptions and reshape unclear problems. It acts as a thinking partner during the investigation phase, ensuring you capture your reasoning and decisions before any implementation begins.

When should I not use exploration-first guidance for requirement clarification?▼

You should not use exploration-first guidance when you are ready to write code or execute feature work. It enforces strict constraints to prevent implementation, serving solely as a tool for thinking through changes and reducing uncertainty.