openspec-explore

Guide teams through open-ended problem exploration and requirement clarification.

221|96|Updated May 18, 2022
One-click install
npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-explore-sap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/SAP/e-mobility-charging-stations-simulator/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-explore-sap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Openspec-explore provides a guided thinking partner to help teams explore ideas, investigate problems, and clarify requirements before making changes or implementing solutions.

Core Features & Use Cases

  • Non-prescriptive thinking partner: Facilitates open-ended exploration, questions, and visual reasoning without enforcing a fixed process.
  • Discovery-oriented workflow: Supports problem understanding, requirements elicitation, and design exploration during early-stage discussions.
  • Decision framing and risk awareness: Helps surface assumptions, risks, and potential design directions to inform next steps.

Quick Start

Start explore mode to think deeply about a problem, surface questions, and outline potential approaches before any implementation.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I facilitate design thinking and clarify requirements during early project discovery?

To facilitate design thinking and clarify requirements, use a guided thinking-partner mode that supports open-ended inquiry, visual reasoning, and problem understanding before any implementation begins.

What is a non-prescriptive thinking partner for requirements elicitation?

A non-prescriptive thinking partner for requirements elicitation is a guided facilitation mode that surfaces questions, assumptions, and risks through open-ended exploration without enforcing a fixed process or generating code.

How do I explore ideas and frame decisions before starting software implementation?

You can explore ideas and frame decisions by starting a discovery-oriented workflow that investigates problems, elicits requirements, and outlines potential design directions to inform your next steps.

Can I use this to generate code or enforce a specific development workflow?

No, you cannot use this to generate code or enforce a specific workflow. It maintains a stance of curiosity and open-ended inquiry, strictly avoiding prescriptive workflows or code generation during early discovery.

Does this approach work for surfacing risks and assumptions during change discussions?

Yes, this approach works for surfacing risks and assumptions during change discussions by providing a guided framework that enforces curiosity and helps teams investigate problems before making changes.