openspec-explore

Explore ideas, requirements, and codebase context to clarify problems before implementation.

22|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill openspec-explore-izzoa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/izzoa/polyrouter/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/izzoa/polyrouter --skill openspec-explore-izzoa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you think through a problem, clarify requirements, and investigate a codebase before making implementation decisions.

Core Features & Use Cases

  • Idea exploration: Brainstorm approaches, challenge assumptions, and compare options for a change or feature.
  • Codebase investigation: Read files, search for patterns, and map architecture to understand how a system works.
  • Requirement clarification: Surface unknowns, risks, and tradeoffs so decisions are grounded in reality.
  • Use case: A user wants to understand a tricky auth flow or compare storage options before starting a change.

Quick Start

Ask the assistant to explore your problem, investigate the relevant codebase, and help you clarify the best path forward.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I investigate a codebase to understand architecture before making changes?

Codebase investigation involves reading files, searching for patterns, and mapping architecture to understand system mechanics. This process clarifies how a system works before implementation decisions are made.

What is the best way to explore ideas and analyze tradeoffs for a new feature?

Idea exploration involves brainstorming approaches, challenging assumptions, and comparing options to surface unknowns and tradeoffs. This ensures your feature requirements are clarified and risks are identified before development starts.

How do I clarify requirements and surface risks for early-stage design discussions?

Clarifying requirements in early-stage design means surfacing unknowns, risks, and tradeoffs through careful reasoning. This grounds your architecture decisions in reality and prevents scope creep during implementation.

Can I scope a complex change without writing any application code first?

Yes, change scoping can be performed without writing application code by reading relevant files and reasoning through the requirements. This allows you to compare approaches and understand the impact before committing to an implementation path.

When do I need to map an existing system architecture before starting a new integration?

You need architecture investigation when facing a tricky flow or complex integration, such as comparing storage options or understanding an auth flow. Mapping the system clarifies requirements and highlights tradeoffs before you build.