Verified:GitHub

openspec-explore

Guide requirement clarification and problem-space exploration before software implementation.

6|2|Updated Feb 10, 2026

Search Tags:#investigation #requirements #exploration #decision support #openspec #tradeoff analysis #architecture mapping

Ready to run

npx skills add https://github.com/LingoJack/jcli --skill openspec-explore-lingojack

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you think through ambiguous requirements, investigate a codebase, and clarify tradeoffs without accidentally jumping into implementation.

Core Features & Use Cases

Exploration-first stance: Enables deep problem-space clarification while explicitly forbidding code changes or feature implementation.
Codebase investigation: Lets you map architecture, find integration points, and surface hidden complexity to ground your thinking.
Option comparison & visualization: Supports brainstorming multiple approaches and expressing them with diagrams and comparison tables.

Quick Start

Use the openspec-explore skill to investigate the problem you want to change and clarify requirements without writing or implementing anything.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify ambiguous software requirements before starting implementation?▼

To clarify ambiguous software requirements before implementation, you can use an exploration-first approach that maps architecture and surfaces tradeoffs. This method enforces an exploration-only stance, permitting codebase analysis while strictly prohibiting feature implementation.

What is the best way to investigate a codebase to surface hidden complexity and integration points?▼

The best way to investigate a codebase for hidden complexity is through active problem-space exploration. This process allows you to map architecture and find integration points to ground your thinking, ensuring you thoroughly understand the system before any changes begin.

Can I compare multiple solution options and visualize tradeoffs during requirement exploration?▼

Yes, you can compare multiple solution options and visualize tradeoffs during requirement exploration. This approach supports brainstorming multiple approaches and expressing them with diagrams and comparison tables to help you evaluate decisions.

Does requirement exploration force me to create OpenSpec artifacts?▼

Requirement exploration does not force you to create OpenSpec artifacts. The process requires optional OpenSpec artifact creation only when explicitly requested, keeping the focus strictly on reading and analysis rather than documentation overhead.

When should I use an exploration-only stance for software changes?▼

You should use an exploration-only stance for software changes during early ideation, active investigation, and mid-change ambiguity resolution. It is essential when tradeoffs and unknowns must be surfaced before committing to any feature implementation.

Why does requirement exploration prohibit writing code and implementing features?▼

Requirement exploration prohibits writing code and implementing features to prevent accidentally jumping into implementation before design is clear. This constraint ensures you safely think through ambiguous requirements, investigate the codebase, and clarify tradeoffs without distraction.