openspec-explore

Analyze project structure and artifacts to surface guiding questions and options.

Updated May 29, 2025

Search Tags:#codebase #requirements #diagramming #exploration #openspec #design-thinking

Ready to run

npx skills add https://github.com/crozzbite/DnDApp --skill openspec-explore-crozzbite

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec exploration mode provides a thinking partner to ideate, analyze problems, and clarify requirements without implementing changes, enabling deeper understanding before committing to a path.

Core Features & Use Cases

Open-ended exploration and idea synthesis with a thinking partner
Grounded analysis by referencing the actual codebase and project context
Surface risks, unknowns, and alternative directions with visual diagrams

Quick Start

Start a discovery session by describing your goal and letting the explorer surface multiple 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 codebase requirements without committing to code changes?▼

You can explore requirements without committing changes by using a non-committal exploration mode that reads project structure and artifacts to surface guiding questions, risks, and alternative directions for your decision.

What is the best way to map exploration paths across open-ended problem spaces?▼

Mapping exploration paths is best done by grounding ideas in the actual codebase and stated goals, letting a thinking partner surface unknowns and multiple directions without implementing changes.

Can I analyze project constraints and dependencies visually before implementation?▼

Yes, you can analyze constraints and dependencies visually by generating diagrams that surface risks and alternative directions, ensuring you understand the problem space before writing implementation code.

How do I start a discovery session to clarify requirements for my current project?▼

Start a discovery session by describing your goal to the explorer and letting it read your current project structure, which surfaces relevant context, constraints, and next steps for you to decide on.

Does non-committal exploration still modify my codebase artifacts?▼

No, non-committal exploration does not modify your codebase artifacts; it maintains a safe environment by reading the project structure and surfacing risks, dependencies, and options without implementing any changes.