openspec-explore

Explore problems and clarify requirements through structured thinking modes.

19|4|Updated Jan 11, 2026

Search Tags:#codebase #requirements #problem-solving #openspec #explore #design-thinking #think

Ready to run

npx skills add https://github.com/ZanebonoAlter/Syntopica --skill openspec-explore-zanebonoalter

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A thinking partner that helps you think through ideas, investigate problems, and clarify requirements before or during changes.

Core Features & Use Cases

Surface questions and alternative paths through open-ended dialogue.
Visualize concepts with ASCII diagrams and contextual exploration of the codebase or problem space.
Surface risks, unknowns, and potential next steps to guide decision making.

Quick Start

Enter explore mode and think deeply with open-ended prompts.

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 explore design options before writing code?▼

To clarify requirements before writing code, use a structured thinking partner to frame problems, prompt open-ended dialogue, and surface alternative paths. This approach investigates the problem space and documents potential paths without writing implementation code.

What is the best way to visually map out a codebase problem space?▼

To visually map out a codebase problem space, apply exploration modes that generate ASCII diagrams. This method contextualizes the problem space, surfaces unknowns, and visualizes concepts to guide your decision-making process.

Can I use design-thinking to investigate codebase risks without implementing changes?▼

Yes, you can use design-thinking to investigate codebase risks without implementing changes. A thinking partner analyzes and documents potential paths while explicitly avoiding implementation or code-writing, ensuring safety by surfacing risks and unknowns first.

How do I frame a problem when I only have a vague idea of what needs fixing?▼

To frame a problem from a vague idea, enter an exploration mode that prompts structured thinking and open-ended dialogue. This surfaces questions, risks, and potential next steps to guide your decision-making before any changes are made.

Does this requirements exploration approach actually write or modify code?▼

No, this requirements exploration approach does not write or modify code. It ensures safety by explicitly avoiding implementation, focusing solely on analyzing the problem space, framing problems, and documenting potential paths for you to act on later.