openspec-explore

Guide problem exploration and requirement clarification with ASCII diagrams and questions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zh-impact/fcollections --skill openspec-explore-zh-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/zh-impact/fcollections/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/zh-impact/fcollections --skill openspec-explore-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to gain a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when you want to think through something before or during a change.

Core Features & Use Cases

  • Guided exploration: prompts questions, surfaces multiple directions, and helps frame problems.
  • Codebase investigation: maps architecture, patterns, and dependencies to improve understanding.
  • Option comparison: sketches tradeoffs and recommendations to aid decision making.
  • Visual communication: encourages ASCII diagrams and clear thinking artifacts to convey ideas.

Quick Start

Describe your problem and I will help you explore it step by step.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore and clarify requirements before writing code?

To explore and clarify requirements, you can use a guided thinking partner that prompts questions, surfaces multiple directions, and frames problems before any implementation begins.

What is the best way to map codebase architecture during early planning?

Mapping codebase architecture during early planning involves investigating patterns and dependencies to improve understanding, often using visual communication like ASCII diagrams to convey ideas.

Can I use this approach to compare design options and tradeoffs?

Yes, you can compare design options by sketching tradeoffs and recommendations, which aids decision making when handling ambiguous goals and exploring multiple directions.

Does this requirements exploration process generate executable code?

No, this requirements exploration process does not generate executable code; it explicitly distinguishes thinking artifacts from executable code and states exploration boundaries with no direct code output.

When should I use a problem framing partner instead of an implementation tool?

Use a problem framing partner during early planning and design discussions when you face ambiguous goals and need to think through ideas, investigate problems, and clarify requirements without implementing features.