skills.rest
sundaiclaw
sundaiclawCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Ask clarifying questions and diagram problems during early-stage planning.

7|2|Updated Mar 8, 2026
Search Tags:#ideation#requirements#problem-solving#explore#thinking-partner#ascii-diagrams
One-click install
npx skills add https://github.com/sundaiclaw/hacker --skill openspec-explore-sundaiclaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/sundaiclaw/hacker/tree/main/agent-build-observatory/.claude/skills/openspec-explore
Command: npx skills add https://github.com/sundaiclaw/hacker --skill openspec-explore-sundaiclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assists users in thinking through problems, exploring options, and clarifying requirements before committing to concrete changes, reducing ambiguity and risk.

Core Features & Use Cases

  • Deep thinking partner that helps articulate goals and constraints
  • Explore multiple directions with clarifying questions and tradeoff analysis
  • Visualize concepts using ASCII diagrams and lightweight sketches
  • Use Case: When planning a project or evaluating requirements, you can rely on this mode to surface questions and potential paths before implementation.

Quick Start

Tell me the problem you'd like to explore and I will think deeply, surface options, and propose next steps.

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 starting a project?▼

Exploring ideas and clarifying requirements involves using a thinking partner to articulate goals, surface risks, and analyze tradeoffs. This process reduces ambiguity and risk before committing to concrete implementation changes.

What is the best way to visualize concepts during early-stage planning?▼

Visualizing concepts during early-stage planning is best done using ASCII diagrams and lightweight sketches. This method clarifies problem structures and explores directions without needing complex modeling tools.

How do I elicit requirements for a product idea without writing code?▼

Eliciting requirements for a product idea without writing code involves adopting a questioning stance to surface unknowns and potential paths. This deep thinking process focuses on problem exploration and tradeoff analysis rather than implementation.

Can I use this problem exploration approach for process improvements?▼

Yes, this problem exploration approach applies to process improvements. It functions as a deep thinking partner across projects and product ideas to surface questions and propose next steps before execution.

Does this requirement exploration method execute code or modify files?▼

No, this requirement exploration method does not execute code or modify files. It refrains from writing or executing code, focusing entirely on deep thinking, asking questions, and visualizing concepts to clarify requirements.

Related Skills

Explore More Education & Research Skills→
deandumdeandum
3

idea-refine

Refine vague ideas into actionable task statements with MVP scope and validation criteria.

Community
Advanced
ssv445ssv445
1

plan-exit-review

Review plans for scope, architecture, and quality gates with actionable recommendations.

Community
Advanced
HmbownHmbown
105

fear

Generate ranked failure modes and mitigations from a plan via structured pre-mortem analysis.

Community
Advanced
genkovichgenkovich
89

specify

Transform feature ideas into detailed product specifications through interactive interviews and validation.

Community
Advanced