openspec-explore

Name: openspec-explore
Availability: InStock
Author: jason23452

Explore codebases and clarify problems through structured thinking without code changes.

Updated Apr 2, 2026

Search Tags:#codebase #requirements #discovery #visualization #openspec #explore #thinking-partner

Ready to run

npx skills add https://github.com/jason23452/n8n --skill openspec-explore-jason23452

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.

This space provides a thinking partner to explore ideas, investigate problems, and clarify requirements without writing code.

Core Features & Use Cases

Structured thinking and open-ended questioning to surface multiple directions.
Codebase exploration support: read context, map architecture, and surface patterns relevant to discussions.
Optional OpenSpec artifact creation (proposals, designs) when asked, not implementation.

Quick Start

Think deeply with the user to map the problem space and surface exploration directions without writing code.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore a codebase to map architecture and clarify requirements without writing code?▼

Codebase exploration to clarify requirements without writing code is facilitated by structured thinking and open-ended questioning. This approach reads context, maps architecture, and surfaces patterns relevant to your discussions while enforcing no code changes.

What is the best way to map out problem spaces and surface multiple directions during discovery?▼

Mapping problem spaces during discovery is best handled by using a thinking partner to surface multiple directions. This method applies structured thinking and open-ended questioning to investigate ideas, visualize freely, and clarify the problem space.

Can I create OpenSpec proposals and designs during requirements discovery?▼

You can create OpenSpec proposals and designs during requirements discovery when explicitly requested. This optional artifact creation captures the structured thinking output without proceeding into actual code implementation or changes.

Does this approach enforce strict no code changes while investigating the codebase?▼

Yes, this approach enforces strict no code changes while investigating the codebase. It isolates exploratory thinking and architecture mapping from implementation, ensuring the primary output remains structured thought and requirements clarification.

When should I use a thinking partner versus starting direct code implementation?▼

Use a thinking partner during the discovery phase to investigate problems, clarify requirements, and surface multiple directions before writing code. It prevents premature implementation by emphasizing structured thinking and problem visualization as the primary output.