skills.rest
OiAnthony
OiAnthonyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explore ideas and clarify requirements before implementation using the openspec CLI.

8|Updated Jan 19, 2026
Search Tags:#architecture#investigation#codebase#requirements#exploration#openspec
One-click install
npx skills add https://github.com/OiAnthony/.agents --skill openspec-explore-oianthony
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/OiAnthony/.agents/tree/main/skills/openspec-explore
Command: npx skills add https://github.com/OiAnthony/.agents --skill openspec-explore-oianthony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you explore ideas, investigate problems, and clarify requirements before committing to implementation. It keeps the conversation focused on discovery so you can understand the real shape of a change without rushing into code.

Core Features & Use Cases

  • Idea exploration: Work through ambiguous problems, challenge assumptions, and compare possible directions.
  • Codebase investigation: Inspect existing files and patterns to understand architecture, integration points, and hidden complexity.
  • Decision support: Compare tradeoffs, surface risks, and identify what information is still missing before a proposal is created.
  • OpenSpec awareness: Review current change context and use it naturally when a project already has active specifications or tasks.

Quick Start

Ask the AI to enter explore mode and help you think through a problem, inspect the codebase, and clarify the requirements before implementation.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore codebase architecture and clarify requirements before implementation?▼

You can explore codebase architecture and clarify requirements by entering an exploration mode that inspects existing files, investigates integration points, and enforces a strict no-implementation stance to focus purely on discovery.

What is the best way to investigate hidden complexity in a codebase before proposing a change?▼

The best way to investigate hidden complexity is to inspect existing file patterns and architecture, allowing you to surface risks and identify missing information before creating a formal proposal.

Can I compare implementation options and tradeoffs without writing any code?▼

Yes, you can compare implementation options and tradeoffs without writing code by using a discovery-focused mode that restricts file modifications while allowing codebase search and artifact capture.

Do I need the openspec CLI to review current change context and specifications?▼

Yes, you need the openspec CLI installed to review current change context, as the exploration mode relies on it to naturally surface active specifications and tasks during your investigation.

How does OpenSpec change context review work during pre-implementation discovery?▼

OpenSpec change context review works by integrating active specifications into your discovery session, providing relevant project context naturally when specifications or tasks already exist in your environment.

Related Skills

Explore More Software Engineering Skills→
ValyntValynt

openspec-apply-change

Automate applying tasks from an OpenSpec change using the OpenSpec CLI.

Official
Advanced
elasticelastic
208

new-entity-requirements

Drafts OpenSpec change proposals for new Terraform entities from API and docs.

Official
Advanced
abdullah1854abdullah1854
1

codebase-navigation

Map codebase structure, dependencies, and architectural patterns.

Community
Intermediate
whatevertogowhatevertogo

openspec-explore

Explores codebases and drafts OpenSpec proposals without writing implementation code.

Community
Intermediate