openspec-explore

Guide problem exploration and requirement clarification with OpenSpec practices.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-explore-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-explore-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode as a thinking partner to help explore ideas, investigate problems, and clarify requirements when planning changes or exploring options.

Core Features & Use Cases

  • Stance: Curious, non-prescriptive guidance that surfaces multiple directions.
  • Visual thinking: ASCII diagrams and sketches to represent ideas and flows.
  • Risk surfacing: Identify unknowns and potential pitfalls to inform decisions.
  • OpenSpec grounding: Provide context-aware prompts and references to ground discussions.

Quick Start

Ask me to start exploring a problem area and I will think aloud, surface questions, and sketch diagrams to map options.

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 frame problems during early project discovery?

To clarify requirements and frame problems, use a thinking partner that surfaces questions and generates multiple directions. It provides exploration prompts and ASCII diagrams to map options and identify unknowns during early discovery.

What is the best way to visually map problem framing options and investigate risks?

Visually mapping problem framing options is best handled by generating ASCII diagrams and sketches to represent ideas and flows. This approach surfaces risks and potential pitfalls by identifying unknowns and structuring reasoning.

How do I start exploring a problem area to surface questions and structure reasoning?

To start exploring a problem area, ask the thinking partner to begin thinking aloud. It will surface relevant questions, sketch diagrams to map options, and provide context-aware prompts grounded in OpenSpec practices to guide discovery.

Does this problem exploration approach provide non-prescriptive guidance for change planning?

Yes, this problem exploration approach provides non-prescriptive guidance for change planning. It maintains a curious stance to surface multiple directions and identify potential pitfalls, ensuring decisions are informed rather than prescribed.

Can I use ASCII diagrams to investigate problems and map flows during requirements gathering?

Yes, you can use ASCII diagrams to investigate problems and map flows during requirements gathering. The visual thinking feature sketches ideas and represents flows to help teams structure reasoning and surface risks effectively.

When should I not use a thinking partner for problem framing and requirements clarification?

You should not use a thinking partner for problem framing when you need definitive answers rather than multiple directions. It offers curious, non-prescriptive guidance to surface questions and unknowns, avoiding strict solution prescription.