openspec-explore

Clarify problems and frame requirements through guided exploratory thinking.

Updated Jan 29, 2026

Search Tags:#codebase #requirements #artifacts #exploration #think-aloud #problem-framing

Ready to run

npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-explore-hongquandev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec Explore mode helps teams think through problems, scope ideas, and uncover requirements by reasoning out loud, without authoring or implementing code.

Core Features & Use Cases

Guided thinking: Facilitates questions, clarifications, and framing to surface assumptions and risks.
Idea exploration: Maps potential directions with ASCII diagrams and non-linear exploration.
Artifact-ready: Suggests open-spec artifacts (proposals, designs, specs) for recording insights without code changes.

Quick Start

Begin the Explore mode to think deeply about a problem and map exploration options without writing code.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore software requirements and frame problems without writing code?▼

To explore software requirements without writing code, use a guided think-aloud process that clarifies problems and surfaces assumptions through targeted questions. This approach maps potential directions using diagrams and suggests creating design artifacts to record insights safely.

What is think-aloud problem framing for early-stage codebase ideation?▼

Think-aloud problem framing for early-stage codebase ideation is an exploratory reasoning process that clarifies project scope and uncovers risks. It facilitates questions and maps potential directions visually, ensuring assumptions are surfaced before committing to implementation.

How do I map codebase artifacts and design specs during requirement discovery?▼

You can map codebase artifacts and design specs during requirement discovery by applying non-linear exploration and ASCII diagrams. This process helps visualize potential directions and suggests recording insights directly into proposals or design specs without modifying code.

Can I scope project ideas and uncover risks before generating any implementation?▼

Yes, you can scope project ideas and uncover risks before implementation by using guided exploratory thinking. This methodology prompts clarifications and frames requirements safely, explicitly avoiding code generation while mapping out potential software directions.

What are the limitations of using exploratory thinking for software requirement discovery?▼

The limitation of exploratory thinking for software requirement discovery is that it strictly avoids code generation and implementation. While excellent for scoping ideas and creating design artifacts, it cannot execute or compile the actual software changes it helps plan.

Does openspec-explore work for mapping existing codebase investigations or only new ideation?▼

OpenSpec Explore works for both existing codebase investigations and new early-stage ideation. It applies guided thinking to clarify problems, map potential directions, and suggest artifacts across any software project phase without authoring code.