openspec-explore

Clarify ideas and requirements through guided, non-implementation thinking.

6|Updated Feb 13, 2021

Search Tags:#requirements #exploration #open-spec #ideas #design-thinking #thinking-partner

Ready to run

npx skills add https://github.com/dezkareid/dezkareid --skill openspec-explore-dezkareid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/dezkareid/dezkareid/tree/main/design-system/design-tokens/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/dezkareid/dezkareid --skill openspec-explore-dezkareid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a collaborative space to think through ideas, investigate problems, and clarify requirements before making changes.

Core Features & Use Cases

Thinking partner that asks clarifying questions and surfaces multiple directions
Visualizes problems with ASCII diagrams and structured reasoning
Supports exploring codebases, requirements, and design decisions without writing code
Surface risks and unknowns to help plan next steps

Quick Start

Enter explore mode and start thinking aloud to surface ideas and clarifications.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify product requirements and frame design problems before writing code?▼

You can clarify product requirements and frame design problems by using a guided exploration partner that asks clarifying questions and surfaces multiple directions without writing code. It helps investigate problems and visualize decisions using ASCII diagrams.

What is the best way to brainstorm and refine ideas for engineering teams?▼

The best way to brainstorm and refine ideas for engineering teams is to enter a non-implementation thinking mode that surfaces risks, unknowns, and ethical boundaries while structuring reasoning to plan next steps safely.

Can I explore codebases and design decisions without generating code?▼

Yes, you can explore codebases and design decisions without generating code. The system enforces non-execution rules and resists code-generation to ensure safe interaction during problem framing and requirements refinement.

How do I visualize problems and structure reasoning during requirements exploration?▼

You visualize problems and structure reasoning during requirements exploration by thinking aloud within a guided session, which generates ASCII diagrams and structured logic to surface unknowns and clarify multiple directions.

What are the limitations of using a thinking partner for requirements refinement?▼

A key limitation of using this thinking partner for requirements refinement is its strict non-implementation constraint. It actively resists code-generation and enforces non-execution rules, meaning it cannot be used to produce functional code.