openspec-explore

Explore ideas and surface assumptions to clarify complex requirements.

2|1|Updated Mar 16, 2026

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

Ready to run

npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-explore-yi-ming-zhao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Yi-ming-Zhao/Fittin/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-explore-yi-ming-zhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to act as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Core Features & Use Cases

Curious, non-prescriptive stance that surfaces multiple threads and questions.
Visual thinking support with ASCII diagrams and system sketches.
Surface risks and unknowns to guide safe exploration and decision making.
OpenSpec awareness: read codebase, explore specs, and surface artifacts without implementing.

Quick Start

Tell me the problem you want to explore, and I will think through it with you.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify complex requirements before starting a design or code change?▼

Clarify complex requirements by entering a thinking partner mode that surfaces assumptions and explores ideas without writing code. It reads the codebase for context and asks questions to guide safe decision making during early-stage changes.

What is the best way to explore ideas and investigate problems without immediately implementing them?▼

Exploring ideas without implementing is best done by investigating problems through a curious, non-prescriptive stance. This approach surfaces risks, unknowns, and multiple threads to guide problem framing and design discussions freely.

Can I generate OpenSpec artifacts while exploring and framing design discussions?▼

You can generate OpenSpec artifacts during exploration by reading codebase context and surfacing specs. This thinking partner optionally produces these artifacts while meeting constraints to think freely without directly implementing the changes.

How do I visualize system architecture and sketches during early-stage problem framing?▼

Visualize system architecture during problem framing by using visual thinking support that generates ASCII diagrams and sketches. This helps map out complex ideas and surface assumptions clearly before committing to a specific design direction.

Does this thinking partner approach work for surfacing risks and unknowns in a codebase?▼

This thinking partner approach works for surfacing risks and unknowns by reading the codebase for context and investigating the problem space. It highlights potential issues to guide safe exploration and informed decision making.

When should I not use an exploration mode for my design and ideation workflow?▼

You should not use exploration mode when you need immediate code implementation rather than problem framing. This approach focuses on clarifying requirements and thinking freely without implementing, so it is unsuited for direct code generation.