openspec-explore

Explore ideas and clarify requirements within software development contexts.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-explore-em-jones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-explore-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a thinking partner to help users explore ideas, investigate problems, and clarify requirements before or during a change, without implementing code.

Core Features & Use Cases

  • Exploratory Thinking: Helps users brainstorm, challenge assumptions, and reframe problems.
  • Codebase Investigation: Maps architecture, finds integration points, and identifies patterns.
  • Option Comparison: Facilitates brainstorming, builds comparison tables, and sketches tradeoffs.
  • Use Case: A user is unsure about the best approach for a new feature. They engage this Skill to discuss potential solutions, visualize different architectures, and understand the trade-offs before committing to an implementation.

Quick Start

Engage the openspec-explore skill to think through the problem of improving user authentication flow.

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 implementing a new feature?

To explore ideas and clarify requirements, you can use a design thinking process to brainstorm solutions, challenge assumptions, and reframe problems before writing any code. This approach visualizes architectures and identifies risks early.

What is the best way to investigate a codebase to map architecture and find integration points?

The best way to investigate a codebase involves mapping the existing architecture, finding integration points, and identifying established patterns. This exploratory process helps clarify how new changes will interact with current system structures.

How do I compare architectural options and sketch tradeoffs for a software project?

To compare architectural options, you can facilitate a brainstorming session to build comparison tables and sketch out specific tradeoffs. This clarifies the strengths and weaknesses of each approach before committing to an implementation.

Can I use this thinking process to challenge assumptions during problem solving without writing code?

Yes, you can use this thinking process to challenge assumptions and facilitate problem solving without writing code. It acts strictly as a thinking partner for requirements clarification and exploratory design rather than direct implementation.

Does this requirements clarification approach support referencing context from an OpenSpec system?

Yes, this requirements clarification approach supports interaction with the OpenSpec system. It provides context awareness and allows artifact referencing to ensure exploratory discussions align with existing project specifications.