openspec-explore

Codebase investigation involves reading repository files, mapping architecture, and identifying integration points to clarify ambiguous requirements. This skill supports exploratory analysis during early-stage or midstream design discussions to surface unknowns and compare options without writing code.

Exploring software architecture involves weighing multiple approaches, constraints, and risks before choosing a path. This skill acts as a thinking partner to work through uncertain technical directions and compare tradeoffs before committing to a specific implementation plan.

Clarifying ambiguous software requirements is the core function of this skill. It investigates open-ended software problems, surfaces unknowns, and unpacks messy feature requests to help you decide whether to refine the plan or create a change proposal.

This skill provides exploratory analysis only and does not generate code. It focuses on investigating design spaces, comparing architectural options, and surfacing risks during early-stage or midstream discussions before any implementation begins.

Creating a change proposal follows comparing multiple approaches, constraints, and risks during exploration. This skill helps you unpack the problem, inspect the existing system, and decide whether to refine the plan or formulate a formal proposal for the next steps.

Exploratory analysis is not suitable when requirements are fully defined and implementation can proceed directly. This skill is designed for early-stage or midstream design discussions where unknowns, tradeoffs, and ambiguous requirements still need to be surfaced and resolved.