openspec-explore

Name: openspec-explore
Availability: InStock
Author: LIDR

Guide structured exploration of ideas, problems, and requirements without writing code.

273|270|Updated Jun 30, 2025

Search Tags:#requirements #exploration #diagrams #brainstorm #open-spec #explore #thinking-partner

Ready to run

npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-explore-lidr-academy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/LIDR-academy/AI4Devs-LTI-extended/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-explore-lidr-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec exploration mode provides a thinking partner to help teams think through ideas, problems, and requirements before committing to changes, reducing ambiguity and rework.

Core Features & Use Cases

Facilitates structured thinking through free-form analysis, questions, and diagrams to map problem space.
Surface risks, unknowns, and assumptions to inform decision-making early in the discovery process.
Supports discovery sessions, design discussions, and requirements clarifications by guiding conversation and generating exploratory artifacts.
Use Case: during a feature proposal, switch to explore mode to outline questions, visualize options, and capture hypotheses without implementing code yet.

Quick Start

Ask the assistant to enter explore mode and begin by outlining questions and visual diagrams.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore ideas and clarify requirements before writing code?▼

You explore ideas and clarify requirements by entering a discovery session where an AI guides you through structured thinking, asks probing questions, and surfaces unknowns. This process maps the problem space and reduces ambiguity before any implementation begins.

What is the best way to brainstorm design discussions across codebases?▼

Brainstorming design discussions across codebases works best by using a thinking partner to read relevant files and suggest hypotheses. This approach visualizes options and captures exploratory artifacts without committing to code changes prematurely.

Can I generate diagrams during a requirements clarification session?▼

Yes, you can generate diagrams during a requirements clarification session. The exploration mode maps the problem space by suggesting visual diagrams alongside free-form analysis to help teams think through ideas and inform decision-making.

Does this requirements exploration mode write or modify code?▼

No, this requirements exploration mode does not write or modify code. It strictly enforces exploration boundaries by focusing on design discussions, outlining questions, and capturing hypotheses, deliberately avoiding all implementation tasks.

When do I need a thinking partner for feature proposals?▼

You need a thinking partner for feature proposals when you want to surface risks, unknowns, and assumptions early in the discovery process. It helps outline questions and visualize options before committing to actual development.

Are there limitations to using AI for brainstorming and requirements exploration?▼

A key limitation is that this AI brainstorming approach is strictly bounded to exploration and will not execute implementation tasks. If your session requires writing code or making file modifications, you must switch to a different mode.