openspec-explore

Explores ideas and investigates codebases as a thinking partner before creating OpenSpec change proposals.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/pablof7z/pod0 --skill openspec-explore-pablof7z
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/pablof7z/pod0/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/pablof7z/pod0 --skill openspec-explore-pablof7z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned designs. This Skill provides a structured exploration mode where the AI acts as a thinking partner—investigating the codebase, visualizing options with diagrams, and clarifying requirements before any code is written. ## Core Features & Use Cases - Exploration stance: Asks open questions, challenges assumptions, compares options with tradeoff tables, and draws ASCII diagrams of architectures, state machines, and data flows. - OpenSpec integration: Reads project context and rules from openspec/config.yaml, checks active changes via openspec list --json, and captures crystallized decisions into proposals, designs, specs, and tasks using the openspec CLI. - Guardrails against premature implementation: Never writes application code in explore mode; it only investigates and optionally scaffolds change artifacts through openspec new change. - Use Case: A developer is unsure whether to use SQLite or Postgres for a CLI tool. The Skill maps constraints, builds a comparison table, recommends a path, and offers to capture the decision in a design artifact. ## Quick Start Ask the agent to enter explore mode and think through whether your planned feature should use approach A or B before creating a change proposal.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore a feature idea before writing code?▼

Invoke explore mode and describe your idea or problem. The agent investigates the codebase, asks clarifying questions, draws diagrams of options, and only captures decisions into OpenSpec artifacts when you ask—it never writes implementation code.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking stance for working through vague ideas, comparing technical approaches, and clarifying requirements. It can read existing change artifacts for context and scaffold new change proposals via the openspec CLI when exploration concludes.

Does openspec-explore require the openspec CLI installed?▼

Yes, the Skill requires the openspec CLI for context commands like `openspec list --json`, `openspec status`, and `openspec new change`. Without a store configured, commands act on the nearest local `openspec/` root directory.

Can explore mode write code or implement features?▼

No, explore mode explicitly forbids writing application code or implementing features. It may only read files, search code, and create OpenSpec artifacts such as proposals, designs, and specs when the user requests capture.

When should I not use explore mode?▼

Skip explore mode when requirements are already clear and you want direct implementation. It is designed for uncertain problem spaces; forcing it onto well-defined tasks adds unnecessary discussion overhead.