openspec-explore

Name: openspec-explore
Availability: InStock
Author: lewisoepwqi

Explore ideas, clarify requirements, and map codebases with ASCII diagrams.

2|Updated Jan 29, 2026

Search Tags:#codebase #guidance #visualization #exploration #open-spec #design-thinking

Ready to run

npx skills add https://github.com/lewisoepwqi/scientific_nini --skill openspec-explore-lewisoepwqi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Core Features & Use Cases

Thinking partner: helps map the codebase, surface questions, and visualize relationships with ASCII diagrams when exploring complex changes.
Non-implementation stance: reminds users to exit explore mode and create a change proposal for any implementation tasks.
OpenSpec artifacts: may generate design artifacts (proposals, designs, specs) to capture thinking without writing production code.
Use Case: When starting a new feature, use openspec-explore to reason about requirements and possible approaches before coding.

Quick Start

Ask the assistant to enter explore mode and begin deep thinking about the problem and potential directions.

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 map my codebase before starting a new feature?▼

To clarify requirements and map your codebase, use a guided exploration partner to reason about potential approaches, surface questions, and visualize relationships before writing production code. This structures early-stage design thinking.

Can I generate design artifacts and specs without writing production code?▼

Yes, you can generate design artifacts like proposals, designs, and specs to capture your thinking without writing production code. This documents requirements and exploration before implementation begins.

What is the best way to visualize complex relationships during codebase exploration?▼

The best way to visualize complex relationships during codebase exploration is using ASCII diagrams generated by a thinking partner. This surfaces questions and maps structural connections when investigating complex changes.

Does this exploration mode handle implementation tasks or just design thinking?▼

This exploration mode handles only design thinking and requirements clarification, not implementation tasks. It explicitly reminds users to exit explore mode and create a change proposal for any actual implementation work.

When do I need OpenSpec guardrails for early-stage design exploration?▼

You need OpenSpec guardrails for early-stage design exploration when you want to structure requirements clarification and map codebase context systematically. This ensures exploration stays aligned with specifications before artifact creation.