openspec-explore

Explore ideas and clarify requirements without implementing changes.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-explore-yandiaan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/yandiaan/penginfo-handal-hackathon/tree/main/.qoder/skills/openspec-explore
Command: npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-explore-yandiaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thinking partner to help you explore ideas, investigate problems, and clarify requirements without directly implementing changes.

Core Features & Use Cases

  • Explore problem space: ask clarifying questions and surface multiple directions to consider.
  • Investigate the codebase and architecture: map dependencies, surface risks, and identify integration points.
  • Visualize ideas: create ASCII diagrams and mental models to communicate options clearly.
  • Surface risks and unknowns: identify potential failure points, data gaps, and assumptions.

Quick Start

Tell me what you want to explore and I will help think through it without implementing 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 and clarify requirements without writing code?

To explore requirements without writing code, use a thinking-partner mode that asks clarifying questions, compares options, and visualizes diagrams while enforcing non-implementation behavior during discovery sessions.

What is the best way to investigate a codebase when problems are vague?

The best way to investigate vague problems is using an exploration mode that reads files, maps dependencies, surfaces integration points, and identifies risks without implementing changes.

Can I visualize architecture and ideas using ASCII diagrams during discovery?

Yes, you can visualize architecture and ideas using ASCII diagrams to build mental models and communicate options clearly during problem-space exploration and requirement clarification.

Does this exploration mode allow creating OpenSpec artifacts?

Yes, this exploration mode permits creating OpenSpec artifacts upon request while displaying guardrails and boundary conditions to ensure no direct code implementation occurs.

What are the limitations of using a thinking partner for problem-solving?

The limitation is that it enforces non-implementation behavior, meaning it will not write or apply code changes. It is restricted to reading files, investigating architecture, and surfacing risks.