skills.rest
hmj1026
hmj1026COMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explore software problems and clarify requirements with OpenSpec CLI.

Updated Nov 26, 2025
Search Tags:#codebase#visualization#exploration#openspec#risk-analysis#problem-space
One-click install
npx skills add https://github.com/hmj1026/docker_run --skill openspec-explore-hmj1026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/hmj1026/docker_run/tree/main/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/hmj1026/docker_run --skill openspec-explore-hmj1026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec exploration mode provides a thinking partner to help teams think through ideas, investigate problems, and clarify requirements without implementing changes.

Core Features & Use Cases

  • Explore the problem space by asking questions, reframing problems, and surfacing multiple directions.
  • Investigate the codebase and project context with diagrams, architecture mapping, and dependency spotting.
  • Visualize workflows and decisions with ASCII diagrams and lightweight schemas to communicate options.
  • Surface risks, unknowns, and dependencies to reduce blind spots and inform next steps.
  • Adapt to evolving user needs by following interesting threads and re-framing scope as needed.

Quick Start

Begin by asking a clarifying question to understand the goal, then guide the exploration.

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 and map architecture during the requirements phase?▼

Codebase exploration involves investigating project context by asking clarifying questions, mapping dependencies, and visualizing workflows with lightweight schemas to clarify requirements without writing executable code.

Can I visualize architecture and workflows without generating implementation code?▼

Yes, you can visualize workflows and decisions using ASCII diagrams and lightweight schemas to communicate options, deliberately surfacing risks and dependencies without producing any executable code output.

What is problem-space analysis and when do I need it for software projects?▼

Problem-space analysis is the process of investigating problems, reframing scope, and surfacing unknowns to reduce blind spots. You need it during brainstorming and requirement clarification before committing to an implementation path.

Does this exploration approach require the OpenSpec CLI to function?▼

Yes, this exploration mode requires the OpenSpec CLI to provide a thinking partner that helps teams think through ideas, investigate problems, and clarify requirements across software projects.

What is the best way to surface risks and unknowns before starting development?▼

The best way to surface risks is by using a thinking partner to investigate the codebase, spot dependencies, and map architecture, reducing blind spots to inform your next steps before development begins.

How do I clarify requirements when project scope is still evolving?▼

Clarify requirements by following interesting threads, asking questions, and reframing scope as needed, allowing the exploration to adapt to evolving user needs throughout the problem-space analysis.

Related Skills

Explore More Education & Research Skills→
TranVanTienDatTranVanTienDat

openspec-explore

Explore project requirements and ideas using OpenSpec artifacts and codebase investigation.

Community
Advanced
knowz-ioknowz-io
1

knowzcode-explore

Analyze project architecture and patterns to generate implementation roadmaps.

Official
Advanced
dual-devs0dual-devs0
1

senior-architect

Generate architecture diagrams and analyze system dependencies with Python.

Community
Advanced
Siamese001Siamese001

ast-first-gate

Builds and validates an AST dependency graph before any code analysis.

Community
Advanced