openspec-explore

Name: openspec-explore
Availability: InStock
Author: YangYuS8

Explore ideas and clarify requirements through structured questioning before implementation.

Updated Mar 7, 2026

Search Tags:#collaboration #requirements #visualization #exploration #open-spec #problem-framing #thinking-partner

Ready to run

npx skills add https://github.com/YangYuS8/blog --skill openspec-explore-yangyus8

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/YangYuS8/blog/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/YangYuS8/blog --skill openspec-explore-yangyus8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

提供一个思考伙伴，帮助用户在进行变更前后进行深入思考、提出澄清性问题、探索不同方向，从而提升决策质量和协作效率。

Core Features & Use Cases

澄清需求：通过提问和结构化推演，快速界定问题边界与目标。
多角度探索：在不同路径之间产生对比与取舍，激发创意。
可视化思维支持：用 ASCII 图表或结构图帮助理解复杂场景。
Use Case：在产品设计初期，与团队共同探讨目标用户、使用场景和衡量指标。

Quick Start

Begin by articulating your exploration goals and questions, so we can collaboratively clarify requirements before making any changes.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore requirements and frame problems before implementing code changes?▼

A collaborative thinking partner helps you explore requirements by asking clarifying questions and structuring your inquiry. It enables iterative problem framing and option evaluation to define boundaries before committing to codebase modifications.

What is the best way to visualize thinking and compare different exploration paths?▼

Visualizing thinking and comparing exploration paths is best achieved using ASCII charts or structured diagrams. This method contrasts different directions and evaluates trade-offs to help understand complex project contexts effectively.

Can I use a structured exploration process for early product design and team collaboration?▼

Yes, structured exploration supports early product design and team collaboration by acting as a thinking partner. It facilitates collaborative discussion on target users, usage scenarios, and success metrics to align the team on problem framing before implementation.

Does this requirements exploration approach generate actual code or implementation plans?▼

No, this requirements exploration approach does not generate code or implementation plans. It operates within non-implementation boundaries, focusing strictly on adaptive persona guidelines, safety constraints, and collaborative problem framing rather than writing code.

How do I start a collaborative thinking session for project requirement clarification?▼

Start a collaborative thinking session for requirement clarification by articulating your exploration goals and questions. This enables the thinking partner to iteratively clarify needs, explore directions, and frame the problem before changes are made.