openspec-explore

Explores ideas and clarifies requirements for OpenSim workflows.

503|60|Updated Sep 7, 2023
One-click install
npx skills add https://github.com/epam/ai-dial-chat --skill openspec-explore-epam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/epam/ai-dial-chat/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/epam/ai-dial-chat --skill openspec-explore-epam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec explore mode provides a thinking partner to help teams think through ideas, investigate problems, and clarify requirements before or during changes.

Core Features & Use Cases

  • Guided thinking: a flexible partner that facilitates questions, diagrams, and scenario exploration.
  • Non-implementation stance: you may read and reason about codebase without writing code, suitable for change proposals and design sprints.
  • Visual thinking aids: ASCII diagrams and structured exploration to surface assumptions and risks.

Quick Start

Start an exploration by asking it to map requirements and outline options before proposing changes.

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 before proposing software changes?

To clarify requirements before changes, use a guided thinking partner to investigate problems, surface questions, and visualize options. This approach aligns with OpenSpec workflows and helps map out assumptions safely without writing code.

Can I explore ideas and map problems during a design sprint without writing code?

Yes, you can explore ideas during a design sprint without writing code. A non-implementation thinking partner reads and reasons about your codebase to guide exploration, facilitating scenario visualization and risk assessment safely.

What is the best way to surface risks and assumptions when investigating a new feature?

The best way to surface risks and assumptions is by using structured exploration with visual thinking aids. Generating ASCII diagrams and facilitating questions helps visualize scenarios and clarify requirements before implementation.

Does this thinking partner work with OpenSpec workflows for change review conversations?

Yes, this thinking partner works directly with OpenSpec workflows. It operates with context awareness during change-review conversations to outline options, surface questions, and guide discovery without implementation.

What are the limitations of using a non-implementation stance for early discovery?

A non-implementation stance for early discovery limits direct code generation. While it reads and reasons about your codebase to facilitate exploration and diagram options, it cannot write, modify, or deploy code changes.

How do I start an exploration session to outline options for a problem?

To start an exploration session, ask the partner to map requirements and outline options before proposing changes. This initiates a structured conversation that uses visual aids to investigate the problem space.