openspec-explore

Explore problem spaces and clarify requirements without writing code.

1|Updated Apr 7, 2026

Search Tags:#codebase #requirements #exploration #open-spec #design-thinking #thinking-partner

Ready to run

npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-explore-lippyydev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/LippyyDev/Agate-Antigravity-Helper-/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-explore-lippyydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a thinking partner that helps teams explore ideas, investigate problems, and clarify requirements without writing code, by reading context, asking questions, and surfacing alternative paths.

Core Features & Use Cases

Thoughtful exploration: think aloud, surface assumptions, and map problem space using diagrams and questions.
Adaptive guidance: adjust to user direction, follow threads, and surface risks or open questions.
Codebase awareness: read and reference the codebase or documents to ground discussions (without implementing changes).

Quick Start

Enter explore mode and think deeply with me as we read files, search code, and explore problems.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore requirements and clarify ideas before writing code?▼

Codebase awareness during requirements exploration means reading existing files, searching code, and referencing documents to ground design discussions. It ensures conversations about needs and alternative paths stay connected to the actual technical context without implementing any code changes.

What is the best way to map a problem space during early design discussions?▼

Yes, you can use design thinking to surface risks and open questions during codebase reviews. By reading context and following logical threads, the process identifies uncertainties and maps alternative paths while strictly avoiding direct code implementation.

Does this requirements exploration approach generate code artifacts?▼

No, this requirements exploration approach does not generate code artifacts. It maintains strict boundaries by avoiding code implementation entirely, offering only non-code artifacts like diagrams and questions when asked to map the problem space.

When do I need a thinking partner for codebase exploration instead of a coding assistant?▼

You need a thinking partner for codebase exploration instead of a coding assistant when you want to investigate problems, surface assumptions, and clarify requirements. It provides adaptive guidance to map options rather than generating or modifying code directly.