openspec-explore

Guide early design discussions with adaptive questions and ASCII diagrams.

Updated Feb 4, 2026

Search Tags:#codebase #requirements #exploration #diagrams #OpenSpec #problem-space #thinking-partner

Ready to run

npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-explore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/memorysaver/agentpit-gg/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a thinking-partner mode to help structure and explore ideas, investigate problems, and clarify requirements before or during changes.

Core Features & Use Cases

Guided reasoning: prompts the user with adaptive questions and visual diagrams to surface assumptions and risks.
Open-ended exploration: maintains open threads, surfaces multiple directions, and avoids prescriptive steps.
Codebase grounding: encourages referencing actual code and architecture when relevant to ground discussions.
Visual reasoning: uses ASCII diagrams to illustrate flows and dependencies.
Practical use case: when starting a new feature, activate explore mode to map problem space and identify constraints before implementing.

Quick Start

To begin, say: "Enter explore mode" and invite the agent to think deeply and visualize potential directions.

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 implementing changes?▼

Exploration mode guides you through structured questioning and visual diagrams to surface assumptions, map the problem space, and clarify requirements before committing to implementation. Enter explore mode to think deeply about constraints and dependencies with your thinking partner.

What's the best way to structure ideas and investigate problems in early design discussions?▼

Guided reasoning with adaptive questions and ASCII diagrams helps structure ideas, investigate problems, and frame requirements. The thinking-partner approach maintains open threads and explores multiple directions without prescriptive steps, grounding discussion in actual codebase context.

Can I use this to map problem space and identify constraints before starting a feature?▼

Yes. Activate explore mode when starting a new feature to map the problem space, identify constraints, and refine requirements. Codebase grounding and visual reasoning help you reference actual architecture and dependencies before design decisions.

Does this approach work for refining requirements across different project contexts?▼

Exploration applies across project contexts—early design discussions, problem framing, and requirement refinement. Open-ended exploration surfaces multiple directions relevant to your specific architecture and constraints without implementing changes.

What happens if I need to visualize flows and dependencies during exploration?▼

ASCII diagrams illustrate flows and dependencies to support visual reasoning. These diagrams surface relationships and risks, helping you and your thinking partner identify assumptions and potential bottlenecks in your design.

How does this differ from moving straight to implementation?▼

Exploration emphasizes thinking deeply and surfacing assumptions before changes. It maintains open inquiry and avoids prescriptive steps, letting you identify risks, constraints, and alternative directions that implementation-first approaches might miss.