openspec-explore

Guide requirement discovery and design exploration in OpenSpec workflows.

139|27|Updated Nov 9, 2014

Search Tags:#requirements #visualization #codebase investigation #tradeoff analysis #open spec #architecture exploration #non-implementation

Ready to run

npx skills add https://github.com/nfe/client-nodejs --skill openspec-explore-nfe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clarify requirements, investigate existing code or context, and reason through design options before making changes—without rushing to implementation.

Core Features & Use Cases

Requirements and solution exploration: Think through ambiguous problems, challenge assumptions, and reframe the work as needed.
Codebase-grounded discovery: Check what exists in the repository and map architecture or integration points when relevant.
Option comparison and visualization: Generate tradeoffs and visual models (e.g., diagrams and tables) to make decisions clearer.
Safe guardrails: Explicitly avoids implementing features or writing code, while allowing OpenSpec artifacts when requested for capturing thinking.

Quick Start

Start explore mode and ask your question or describe what you’re trying to change, then use it to investigate and reason before implementing.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore architecture and map integration points before writing code?▼

Codebase investigation before implementation involves reading existing files to map architecture and integration points. This Skill enforces a non-implementing stance, allowing you to reason through design options safely without writing application code.

What is the best way to visualize tradeoffs during ambiguous planning?▼

Visualizing tradeoffs during ambiguous planning requires generating diagrams and tables to make decisions clearer. This Skill guides requirement discovery and generates visual models to compare options while explicitly avoiding feature implementation.

How do I document design exploration without writing application code?▼

Documenting design exploration without writing application code is achieved by creating OpenSpec artifacts. This Skill enforces constraints that it may read files or capture thinking in artifacts but must never implement features.

Do I need the openspec CLI to perform requirement discovery and tradeoff analysis?▼

Requirement discovery and tradeoff analysis using this workflow requires openspec CLI awareness. The Skill operates within an OpenSpec-enabled workflow to guide safe design exploration before starting changes.

When should I avoid using a non-implementing stance for debugging investigations?▼

A non-implementing stance for debugging investigations should be avoided when you are ready to apply code fixes. This Skill is designed for reasoning through ambiguous problems and mapping context before starting changes, not for writing the actual fixes.