skills.rest
ybenitezf
ybenitezfCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explores engineering and business problems through guided, interactive dialogue.

Updated Apr 6, 2026
Search Tags:#ideation#requirements#openspec#explore#thinking-partner#guided-thinking
One-click install
npx skills add https://github.com/ybenitezf/pi-github --skill openspec-explore-ybenitezf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/ybenitezf/pi-github/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/ybenitezf/pi-github --skill openspec-explore-ybenitezf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The openspec-explore skill provides a thinking partner that helps users explore ideas, investigate problems, and clarify requirements without implementing code, guiding thoughtful planning and problem framing.

Core Features & Use Cases

  • Think partner for ideation, problem framing, and requirement clarification.
  • Visualize ideas with diagrams and exploratory prompts, without producing production code.
  • Supports surface risks, questions, and open threads to inform change proposals or design artifacts when requested.

Quick Start

Ask me to enter explore mode and think through a problem together.

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 frame a problem before writing code?▼

To clarify requirements and frame a problem, you can use a guided thinking partner to explore ideas, surface risks, and investigate open threads without producing production code. This keeps early-stage ideation focused on design.

Can I explore and investigate a codebase without implementing changes?▼

Yes, you can explore and investigate a codebase without implementing changes by using a non-implementation stance. This approach supports open-ended investigation and problem framing before any actual development begins.

What is the best way to structure early-stage ideation for software design?▼

The best way to structure early-stage ideation is through open-ended exploration with a thinking partner. This process helps visualize ideas with diagrams and exploratory prompts to thoroughly map out requirements and risks.

Does this exploration process create design artifacts or requirement documents?▼

The exploration process optionally creates design artifacts. After surfacing risks and open threads, it can inform change proposals or generate OpenSpec artifacts when explicitly requested during the ideation phase.

How do I start exploring a problem with a thinking partner?▼

To start exploring a problem with a thinking partner, simply ask to enter explore mode. This initiates a guided, open-ended process to think through the problem together and frame requirements effectively.

Related Skills

Explore More Education & Research Skills→
guillaumejayguillaumejay

openspec-explore

Structures exploration of complex problems through guided, codebase-aware thinking sessions.

Community
Advanced
artagonartagon

openspec-explore

Explore ideas and clarify requirements without implementing code changes.

Official
Basic
jacobcyjacobcy
6

openspec-explore

Guide teams through open-ended problem exploration to clarify requirements and surface design options.

Community
Intermediate
hmj1026hmj1026

openspec-explore

Explore software problems and clarify requirements with OpenSpec CLI.

Community
Advanced