openspec-explore

Facilitates exploratory thinking and requirements discovery for proposed OpenSpec changes.

54|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-explore-mrclrchtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/mrclrchtr/SuPi/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-explore-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a focused, read-first thinking partner to help teams and individuals explore ideas, clarify requirements, and surface risks before any implementation or coding begins. It prevents premature implementation by emphasizing discovery, context-gathering, and decision framing tied to existing repository and OpenSpec artifacts.

Core Features & Use Cases

  • Guided discovery sessions: Ask adaptive clarifying questions, challenge assumptions, and reframe problems to reveal hidden requirements.
  • Repository-grounded investigation: Read and reference OpenSpec artifacts and code to map architecture, integration points, and existing constraints.
  • Option comparison and visualization: Brainstorm multiple approaches, sketch tradeoffs and diagrams (ASCII-friendly), and surface risks and unknowns.
  • Capture-ready suggestions: Offer to create proposals, design notes, or specification updates while strictly avoiding writing application code.

Quick Start

Start an explore session to investigate and clarify requirements for a proposed OpenSpec change by asking targeted questions, mapping options, and surfacing risks.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify requirements for a proposed change before writing code?

No, it operates under a strict no-implementation guardrail and never writes application code. It produces proposals, diagrams, and decision summaries specifically to prevent premature implementation.

What is the best way to discover hidden requirements during early-stage design?

The best way to discover hidden requirements is through guided discovery sessions that challenge assumptions and reframe problems. This approach maps architecture and integration points to reveal constraints early in the design phase.

How do I map context and integration points using OpenSpec artifacts?

You can map context and integration points by running a read-only investigation on your repository files and OpenSpec artifacts. This grounds your exploration in existing architecture and constraints without modifying the codebase.

Can I compare design options and visualize tradeoffs without implementing code?

Yes, you can brainstorm multiple approaches and sketch tradeoffs using ASCII-friendly diagrams. This option comparison visualizes risks and unknowns while strictly avoiding writing any application code.

Does requirements exploration work for architecture discussions and investigation?

Yes, requirements exploration is designed for early-stage architecture discussions and investigation. It maps context, asks clarifying questions, and produces capture-ready suggestions like specification updates.