openspec-explore

Explore requirements, tradeoffs, and codebase context before implementation.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-explore-brandon-setegn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-explore-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you think through a problem before committing to implementation, especially when requirements are unclear, tradeoffs matter, or the codebase needs careful investigation.

Core Features & Use Cases

  • Requirements Exploration: Clarify goals, constraints, and open questions before making changes.
  • Codebase Investigation: Read files, inspect patterns, and map architecture to understand where a change fits.
  • Option Comparison: Weigh approaches, surface risks, and compare tradeoffs with diagrams or structured analysis.
  • Use Case: A user wants to add a new capability but is unsure about the best design; this Skill helps explore the space, identify hidden complexity, and prepare for a change proposal.

Quick Start

Ask the AI to explore your problem, inspect the relevant code, and help you compare options before starting 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 before starting implementation?

Codebase exploration involves reading files, inspecting patterns, and mapping architecture to understand where a change fits before writing application code. This Skill helps you investigate existing repositories, clarify requirements, and surface hidden complexity early.

What is the best way to compare architecture tradeoffs for a new feature?

Comparing architecture tradeoffs requires weighing approaches, surfacing risks, and evaluating options with structured analysis or diagrams. This Skill helps you frame the problem and compare design choices before committing to a specific implementation path.

How do I clarify requirements and constraints before making codebase changes?

Clarifying requirements involves identifying goals, constraints, and open questions before modifying a codebase. This Skill helps you think through the problem space, explore tradeoffs, and prepare a structured change proposal without writing application code.

Can I use this to investigate an existing repository before proposing a change?

Yes, investigating an existing repository is a core use case. This Skill reads files, inspects patterns, and maps architecture to understand where a new capability fits, helping you explore the space and prepare for a change proposal.

Does this Skill write application code during the exploration phase?

No, this Skill does not write application code. It focuses on careful reading of files and structured reasoning to explore requirements, tradeoffs, and codebase context before implementation begins.

When do I need to explore requirements and tradeoffs instead of building immediately?

You need requirements exploration when goals are unclear, tradeoffs matter, or the codebase requires careful investigation. This Skill helps you frame the problem, identify hidden complexity, and compare options before committing to implementation.