openspec-explore

Name: openspec-explore
Availability: InStock
Author: nuomi1

Explores problems and clarifies requirements by examining codebases and generating ASCII diagrams.

Updated Apr 9, 2026

Search Tags:#codebase #requirements #open-spec #diagram #explore #idea #thinking-partner

Ready to run

npx skills add https://github.com/nuomi1/vCalendar --skill openspec-explore-nuomi1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a disciplined, thinking-only exploration mode that helps teams think through problems, clarify requirements, and surface design directions without writing code.

Core Features & Use Cases

Explore the problem space by asking clarifying questions, challenging assumptions, and sketching multiple directions.
Investigate the codebase and context by mapping architecture, identifying integration points, and surfacing patterns.
Surface risks, unknowns, and optional experiments with ASCII diagrams and thought experiments.

Quick Start

Describe your problem and ask it to explore the codebase to surface questions and diagrams.

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 explore ideas without writing implementation code?▼

To clarify requirements and explore ideas without writing code, use a thinking partner that maps architecture, surfaces risks, and captures insights through disciplined questioning and ASCII diagrams. This mode focuses on problem framing and design ideation across software and product domains.

What is the best way to map codebase architecture and identify integration points?▼

The best way to map codebase architecture and identify integration points is by exploring the codebase with a thinking partner that reads files, examines patterns, and generates ASCII diagrams to surface questions and open design directions.

Can I generate ASCII diagrams for software design and thought experiments?▼

Yes, you can generate ASCII diagrams for software design and thought experiments. The exploration process sketches multiple directions, surfaces unknowns, and visually maps architecture to help teams frame problems and capture insights.

Does this requirements discovery approach support data and product domains?▼

Yes, this requirements discovery approach supports data and product domains. It applies during early-stage problem framing across software, data, and product contexts, asking clarifying questions and challenging assumptions to surface design directions.

When should I not use a thinking partner for problem framing?▼

You should not use a thinking partner for problem framing when you need to implement code rather than explore ideas. This approach is strictly for requirements discovery, design ideation, and surfacing risks without writing any implementation code.