skills.rest
Lerr1uqs
Lerr1uqsCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explore user problems and design considerations without committing to implementation.

Updated Mar 21, 2026
Search Tags:#problem-solving#exploration#diagrams#openspec#design-thinking#open-ended#thinking-partner
One-click install
npx skills add https://github.com/Lerr1uqs/openjarvis --skill openspec-explore-lerr1uqs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Lerr1uqs/openjarvis/tree/main/.codex/skills/openspec-explore
Command: npx skills add https://github.com/Lerr1uqs/openjarvis --skill openspec-explore-lerr1uqs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, non-implementation thinking partner to explore ideas, diagnose problems, and clarify requirements, helping teams think more deeply before committing to changes.

Core Features & Use Cases

  • Guided exploration: Facilitates open-ended thinking, questions, and diagrams to surface assumptions and risks.
  • Problem clarification: Helps define scope, constraints, and success criteria for new initiatives.
  • Use Case: When planning a feature, use this mode to map the problem, ask clarifying questions, and surface design options without proposing code.

Quick Start

Begin by clarifying the user's goal, map the problem space with diagrams, and think aloud before proposing any changes.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
What is open-ended problem exploration for design thinking?▼

To explore design considerations without writing code, start by clarifying the user's goal. Map the problem space using diagrams, ask open-ended questions to surface risks, and think aloud to define scope and success criteria before proposing any changes.

How do I explore design considerations without writing code?▼

To explore design considerations without writing code, start by clarifying the user's goal. Map the problem space using diagrams, ask open-ended questions to surface risks, and think aloud to define scope and success criteria before proposing any changes.

Can I use diagrams to brainstorm requirements and map the problem space?▼

No prerequisite environment is needed. This approach is applicable whenever teams need a patient thinking partner for brainstorming, requirement elicitation, and design discussions where deep reasoning and open-ended questions are valuable.

Do I need any specific tools or frameworks for requirement elicitation?▼

No prerequisite environment is needed. This approach is applicable whenever teams need a patient thinking partner for brainstorming, requirement elicitation, and design discussions where deep reasoning and open-ended questions are valuable.

What are the limitations of non-implementation exploration?▼

The limitation of non-implementation exploration is that it avoids code changes entirely. It is designed strictly for diagnosing problems and clarifying requirements, so it will not generate, modify, or commit any implementation code.

Related Skills

Explore More Design & Creative Skills→
labs21-devlabs21-dev
28

feature-spec

Draft PRD-style feature specifications with goals, metrics, and open questions.

Official
Advanced
ivanrvpereiraivanrvpereira
17

brainstorming

Turn vague ideas into approved design documents before implementation.

Community
Advanced
ddttomddttom
2

canvas-design

Generate visual art and designs as PNG or PDF files from abstract philosophies.

Community
Basic
mori-shin-xmori-shin-x
12

speckit-clarify

Identify and resolve ambiguities in feature specifications through structured requirement analysis.

Community
Advanced