openspec-explore

Clarify software development ideas and investigate codebase problems before implementation.

4|9|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-explore-datadave-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/DataDave-Dev/weftmap/tree/main/.codex/skills/openspec-explore
Command: npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-explore-datadave-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users clarify ideas, investigate problems, and understand codebases before committing to implementation work, reducing premature decisions and overlooked requirements.

Core Features & Use Cases

  • Guided Exploration: Act as a curious thinking partner that surfaces assumptions, risks, open questions, and alternative approaches.
  • Codebase Investigation: Read files, trace architecture, identify integration points, and ground discussions in the actual repository.
  • OpenSpec Awareness: Inspect active changes and help capture decisions, requirements, scope changes, and follow-up work in the appropriate OpenSpec artifacts.
  • Use Case: When planning a new feature or investigating a complex issue, use this Skill to map the existing system, compare implementation options, and determine whether the work is ready for a formal change proposal.

Quick Start

Use the openspec-explore skill to investigate the current codebase and help clarify the requirements, risks, and possible approaches for my proposed change.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify requirements and investigate a codebase before starting implementation?

To clarify requirements and investigate a codebase before implementation, you can use guided exploration to read files, trace architecture, identify integration points, and surface assumptions, risks, and alternative approaches.

What is the best way to analyze software architecture and compare implementation options for a new feature?

Analyzing software architecture and comparing implementation options involves mapping the existing system to ground discussions in the actual repository, helping you determine if the proposed change is ready for a formal proposal.

Do I need the OpenSpec CLI to explore codebases and plan changes?

Yes, you need the OpenSpec CLI when interacting with registered stores, changes, instructions, specifications, or related artifacts to capture decisions, requirements, and scope changes during codebase exploration.

How does architecture analysis help prevent overlooked requirements during feature discovery?

Architecture analysis prevents overlooked requirements by acting as a curious thinking partner that surfaces hidden assumptions, open questions, and integration risks before committing to premature implementation decisions.

Can I use this approach to map existing systems for technical discovery and change planning?

Yes, you can use codebase investigation for technical discovery and change planning by tracing architecture, identifying integration points, and capturing follow-up work in appropriate OpenSpec artifacts.