openspec-explore

Explore codebases and design questions without implementing changes.

Updated Feb 14, 2026

Search Tags:#architecture #codebase #requirements #visualization #explore #thinking-partner #design-discussion

Ready to run

npx skills add https://github.com/OpenElementsLabs/Octobird --skill openspec-explore-openelementslabs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables users to think through complex ideas and codebases with a guided thinking partner that reads files, searches code, and investigates problems without implementing changes.

Core Features & Use Cases

Guided exploration: surface multiple approaches, ask clarifying questions, and surface risks while staying out of implementation.
Codebase awareness: read relevant files and diagrams to understand context without modifying code.
OpenSpec artifact guidance: propose design surfaces, spike tasks, and surface decisions for a future change.

Quick Start

Start explore mode and ask the AI to think deeply, read relevant files, surface questions, and visualize options before any implementation.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore architecture and requirements in a codebase before writing any code?▼

To explore architecture and requirements without writing code, use a thinking partner skill that reads files, searches code, and investigates problems to surface questions and visualize options. It guides open-ended thinking and clarifies design decisions while staying out of implementation.

What is the best way to visualize design options for complex software problems?▼

The best way to visualize design options for complex software problems is by using an exploration thinking partner that surfaces multiple approaches and clarifies questions. It reads relevant files and diagrams to understand context, helping you map out decisions without modifying code.

Can I use this to gather requirements and clarify design decisions for a new feature?▼

Yes, you can use it to gather requirements and clarify design decisions for a new feature. It acts as a guided thinking partner that investigates problems, surfaces risks, and proposes design surfaces or spike tasks for future changes without implementing anything.

Does this exploration tool modify my codebase while analyzing files?▼

No, this exploration tool does not modify your codebase while analyzing files. It reads relevant files and diagrams to build context and understand the architecture, ensuring your code remains untouched while you investigate problems and surface design artifacts.

How do I start a design discussion to surface risks and approaches for my project?▼

To start a design discussion and surface risks, initiate explore mode and ask the AI to think deeply about your project. It will read relevant files, ask clarifying questions, surface multiple approaches, and visualize options before any implementation begins.

When should I not use a thinking partner for codebase exploration?▼

You should not use a thinking partner for codebase exploration when you need to actually implement changes or write code. This skill is strictly for problem clarification, requirements gathering, and visualizing design options, not for executing code modifications.