openspec-explore

Clarify software ideas, requirements, and implementation problems before coding.

15|Updated Feb 14, 2026

Search Tags:#architecture #requirements #design analysis #openspec #codebase exploration #risk discovery

Ready to run

npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-explore-mahoushoujyo-eee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/mahoushoujyo-eee/eshell/tree/main/.codex/skills/openspec-explore
Command: npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-explore-mahoushoujyo-eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users turn vague ideas, unclear requirements, and difficult implementation questions into grounded understanding before code is written.

Core Features & Use Cases

Problem Exploration: Investigate assumptions, clarify goals, reframe challenges, and surface open questions.
Codebase Investigation: Read files, map architecture, identify integration points, and uncover hidden complexity without modifying application code.
Option Analysis: Compare approaches, visualize tradeoffs, identify risks, and capture decisions in OpenSpec artifacts when requested.
Use Case: When a feature request becomes more complex than expected, use this Skill to trace the existing architecture, compare implementation paths, and decide whether to update a proposal or design.

Quick Start

Use the openspec-explore skill to investigate the existing architecture for the feature I am considering and summarize the key risks, options, and open questions without implementing anything.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify vague software requirements before starting implementation?▼

To investigate existing codebase architecture for a new feature, you can read files, map integration points, and uncover hidden complexity without modifying application code. This process identifies key risks and open questions before you proceed.

What is the best way to compare design options and identify architectural risks?▼

The best way to compare design options and identify risks is to analyze approaches, visualize tradeoffs, and capture decisions in OpenSpec artifacts. This allows you to evaluate implementation paths against the current architecture systematically.

Does the openspec-explore skill modify my application code during analysis?▼

No, the openspec-explore skill does not modify application code during analysis. It explicitly prohibits application code implementation, permitting only repository reading and artifact creation to ensure a safe, read-only investigation of your architecture.

Do I need the OpenSpec CLI to use this skill for requirements exploration?▼

You need the OpenSpec CLI installed if you plan to check active changes during requirements exploration. The CLI is specifically required for managing and interacting with active OpenSpec change planning workflows.

When should I not use codebase exploration for my software design analysis?▼

You should not use codebase exploration for software design analysis when you are ready to write or modify application code. This approach is strictly for clarifying ideas, comparing options, and planning changes rather than implementing the actual solution.