openspec-explore

Explore ideas and clarify requirements with guided prompts and risk identification.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-explore-yager-42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-explore
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-explore-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Think deeply with a partner to explore ideas and clarify requirements before making changes.

Core Features & Use Cases

  • Idea exploration and problem framing
  • Open-ended, non-prescriptive thinking with visual aids
  • Surface questions, dependencies, and risks to guide decision making

Quick Start

Describe your idea or problem, and I will help you explore it step by step.

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?

To explore ideas and clarify requirements, describe your problem to a thinking partner that helps surface questions, options, and risks. This open-ended workflow uses guided prompts and ASCII visuals to support problem framing and decision making without writing code.

What is the best way to frame a problem during early project discovery?

Problem framing during early discovery involves using a flexible, cognitive workflow to identify dependencies and risks. A thinking partner guides you step by step through open-ended questions and visual aids to ensure your team understands the problem space before making changes.

Can I use visual aids to map out project risks and dependencies?

Yes, you can use ASCII visuals to map out project risks and dependencies. The exploration process includes generating visual aids and guided prompts to help teams identify potential risks and surface questions across projects.

Do I need any coding environment to surface questions and options for decision making?

No, you do not need a coding environment to surface questions and options for decision making. The workflow operates entirely as a non-prescriptive cognitive process, focusing on idea exploration and risk identification without writing any code.

When should I use an open-ended thinking partner instead of a structured planning tool?

Use an open-ended thinking partner when you need to explore ideas and clarify requirements before making changes, rather than executing a predefined plan. It is best suited for early discovery and problem framing where surfacing questions and risks is more important than strict structure.