openspec-explore

Guide idea exploration and requirement clarification within the OpenSpec system.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/rfhayn/forager --skill openspec-explore-rfhayn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/rfhayn/forager --skill openspec-explore-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of exploring ideas and developing change proposals within the OpenSpec system, enhancing collaboration and efficiency.

Core Features & Use Cases

  • Exploration and Clarification: Assists in exploring problems and clarifying requirements with a conversational approach.
  • Codebase Investigation: Helps to map architecture, identify integration points, and understand existing patterns.
  • Option Comparison: Provides a framework for brainstorming, comparing, and recommending paths based on the current context.
  • Visualization: Supports the use of ASCII diagrams for clarity in complex scenarios.
  • Risk Surface: Identifies potential risks and unknowns, guiding the user to mitigate them.

Quick Start

Start exploring ideas by initializing the skill with 'open spec explore'.

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 for a change proposal in OpenSpec?

To explore ideas and clarify requirements for an OpenSpec change proposal, you initialize the system conversationally to investigate the codebase, identify patterns, and map integration points. This interactive process helps solidify your change proposal context.

Does the OpenSpec change proposal process require the OpenSpec CLI?

Yes, the OpenSpec change proposal process requires the OpenSpec CLI. The CLI dependency is essential for executing artifact creation and developing the change proposals generated during your conversational exploration sessions.

How do I map codebase architecture and identify integration points before proposing changes?

You can map codebase architecture and identify integration points by using the conversational exploration interface. It guides you through existing code patterns and supports visualization with ASCII diagrams to clarify complex architectural scenarios.

What is the best way to compare options and identify risk surfaces when planning code changes?

The best way to compare options and identify risk surfaces is using the built-in framework for brainstorming and recommending paths. It evaluates current context to highlight potential risks and unknowns, guiding you to mitigate them effectively.

Can I visualize complex codebase scenarios while developing requirements in OpenSpec?

Yes, you can visualize complex codebase scenarios while developing requirements in OpenSpec. The exploration interface supports the use of ASCII diagrams to provide clarity when mapping architecture and understanding integration points.