openspec-explore

Explore codebases to surface questions, risks, and design implications.

17|1|Updated Mar 14, 2025

Search Tags:#codebase #requirements #visualization #explore #problem-framing #thinking-partner

Ready to run

npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill openspec-explore-deckgl-fiber-renderer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/deckgl-fiber-renderer/fiber.gl/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill openspec-explore-deckgl-fiber-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thinking partner to explore ideas, investigate problems, and clarify requirements before making changes.

Core Features & Use Cases

Guided ideation and problem framing to surface questions, risks, and potential solutions.
Non-implementation thinking space that reads code, searches context, and visualizes dependencies with ASCII diagrams.
Supports decision-making workflows and surface-only artifacts (questions, risks, and design notes) until a change proposal is warranted.

Quick Start

Describe the challenge and I will begin an open-ended exploration to surface questions, risks, and 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 before making codebase changes?▼

To clarify requirements and frame problems, you can use a guided exploration partner to surface questions, risks, and design implications. This approach investigates your codebase and decision space to support ideation without generating code or automated changes.

What is the best way to explore a codebase and visualize dependencies during ideation?▼

Exploring a codebase during ideation involves reading code, searching context, and visualizing dependencies with ASCII diagrams. This process creates a non-implementation thinking space to surface risks and design notes until a change proposal is warranted.

How do I start a guided exploration session for project decision-making?▼

To start a guided exploration session, describe the challenge you are facing. The exploration will then begin surfacing open-ended questions, potential risks, and available options to support your decision-making workflow.

Can I use this approach to generate code or apply automated changes to my project?▼

No, you cannot use this approach to generate code or apply automated changes. It serves strictly as a non-implementation thinking space that produces surface-only artifacts like questions, risks, and design notes for decision-making.

Does this thinking partner workflow support open-ended ideation across different projects?▼

Yes, this thinking partner workflow supports open-ended ideation, requirements clarification, and problem framing sessions across projects. It applies to diverse decision spaces by surfacing relevant questions and design implications.