openspec-explore

Explore requirements and design options without writing application code.

5|Updated Apr 29, 2026

Search Tags:#design thinking #requirements #exploration #OpenSpec #codebase investigation #risk analysis #non-implementation

Ready to run

npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-explore-breuerfelix

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Openspec-explore helps you clarify requirements, investigate issues, and explore ideas so you can make better decisions before committing to implementation.

Core Features & Use Cases

Exploration-first thinking: Guides you to investigate and reason about problems without writing code or building features.
Codebase-informed inquiry: Encourages reading and searching the repository to ground your understanding and find integration points.
Option and risk mapping: Supports comparing approaches, surfacing unknowns, and visualizing ideas with diagrams.
Context-aware OpenSpec workflow: Helps you reference existing proposals/designs/tasks and offers to capture new decisions when you’re ready.

Quick Start

Ask it to explore your change safely by saying: "Help me think through how to approach [problem] and what we should verify 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 software design options before writing code?▼

To explore design options before writing code, use a thinking-first approach that clarifies requirements and maps risks without implementation. This allows you to read the codebase, compare approaches, and capture decisions in OpenSpec proposals before committing to application code.

What is the best way to clarify requirements mid-change without implementing features?▼

Clarifying requirements mid-change without implementing features involves applying exploratory reasoning to investigate problems and surface unknowns. By enforcing thinking-only behavior, you can map design options and update OpenSpec specifications without writing application code.

Can I investigate codebase integration points for refactoring planning without modifying files?▼

Yes, you can investigate codebase integration points for refactoring planning without modifying files by reading and searching the repository. This grounds your understanding of the current architecture and helps visualize ideas safely during the ideation phase.

Does OpenSpec support capturing design decisions during troubleshooting?▼

OpenSpec supports capturing design decisions during troubleshooting by allowing the creation of proposals, designs, and specs. It helps you reference existing artifacts and offers to record new decisions when you are ready, keeping exploration strictly separate from implementation.

When should I avoid writing application code during problem investigation?▼

You should avoid writing application code during problem investigation when you are still in the ideation, refactoring planning, or requirement discovery phase. Enforcing thinking-only behavior ensures you fully map risks and options before any implementation begins.