openspec-explore

Guide structured exploration and requirement framing for ambiguous software problems.

2|Updated Feb 5, 2026

Search Tags:#codebase #requirements #discovery #exploration #open-spec #thinking-partner

Ready to run

npx skills add https://github.com/dshearer/misatay --skill openspec-explore-dshearer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/dshearer/misatay/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/dshearer/misatay --skill openspec-explore-dshearer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec exploration mode helps teams think deeply about problems before committing to changes, reducing misalignment and rework.

Core Features & Use Cases

Guided prompts and questions that surface assumptions and constraints.
Visual thinking support with ASCII diagrams and lightweight modeling.
Context-aware exploration that references the codebase and project constraints to keep discussions grounded.
Surface risks, unknowns, and trade-offs to guide decision-making.

Quick Start

Describe your ambiguous problem and ask me to think aloud and visualize options.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify ambiguous software requirements before committing to code changes?▼

To clarify ambiguous software requirements, you can use guided exploration to surface hidden assumptions, frame constraints, and visualize options with ASCII diagrams before writing code. This structured problem analysis reduces team misalignment and prevents downstream rework.

What is the best way to explore and scope a codebase during early design discussions?▼

Exploring and scoping a codebase during early design discussions is best done through context-aware exploration that references project constraints. This approach keeps conversations grounded, surfaces unknowns and trade-offs, and helps teams think deeply about problems before implementation.

How do I identify risks and open questions during project scoping?▼

To identify risks and open questions during project scoping, engage in structured exploration with guided prompts that challenge assumptions. This process surfaces constraints and trade-offs early, providing decision-making guardrails that prevent unexpected issues during development.

Can I use structured exploration to visualize software architecture options without diagramming tools?▼

Yes, you can visualize software architecture options without external diagramming tools by using lightweight ASCII modeling. This visual thinking support allows you to think aloud, map out structural options, and evaluate design trade-offs directly within your text environment.

Does requirement framing work for analyzing problems across multiple teams?▼

Requirement framing works effectively for analyzing problems across multiple teams by providing shared context grounding and structured guardrails. It helps align diverse stakeholders by surfacing constraints and open questions, ensuring everyone understands the problem space before changes.

When should I not use structured exploration for problem analysis?▼

You should avoid structured exploration for problem analysis when the requirements are already fully defined and unambiguous. If there are no open trade-offs to evaluate or assumptions to surface, committing directly to implementation is more efficient than framing the problem.