openspec-explore

Explores ideas, investigates codebases, and clarifies requirements before creating OpenSpec change proposals.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-explore-ssttkkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/ssttkkl/finance-tracker/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-explore-ssttkkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned requirements. This Skill provides a dedicated thinking mode where you can investigate the codebase, compare approaches, visualize architecture, and crystallize decisions before committing to a change proposal. ## Core Features & Use Cases - Codebase-grounded exploration: Reads existing code and OpenSpec artifacts to map architecture, find integration points, and surface hidden complexity. - Visual thinking: Produces ASCII diagrams, comparison tables, and state machines to clarify system behavior and tradeoffs. - OpenSpec integration: Checks active changes via the openspec CLI, reads existing proposals and specs, and offers to capture decisions into design.md, specs, or tasks.md. - Use Case: Before adding real-time collaboration to your app, use explore mode to map the current sync architecture, compare CRDT versus presence-based approaches, and capture the chosen design decision in a change proposal. ## Quick Start Ask the assistant to enter explore mode and think through whether Postgres or SQLite fits your CLI tool before writing any code.

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?

Enter explore mode and describe your idea or problem. The assistant investigates the relevant codebase, draws diagrams of the current architecture, compares implementation options, and helps crystallize requirements before you create a formal change proposal.

What is the difference between explore mode and implementing a change?

Explore mode is strictly for thinking: reading code, asking questions, and comparing approaches without writing application code. Implementation happens after you exit explore mode and create an OpenSpec change proposal with defined tasks.

Does openspec-explore require the openspec CLI?

Yes, the Skill requires the openspec CLI installed on the machine. It uses commands like openspec list, status, and show to read project context, active changes, and existing artifacts, and supports multi-store setups via the --store flag.

Can explore mode update my OpenSpec design or spec files?

Yes, capturing decisions in OpenSpec artifacts like design.md, specs, proposal.md, or tasks.md is allowed since that records thinking rather than implementing code. The assistant offers to capture insights but never modifies artifacts without your approval.

When should I not use explore mode?

Avoid explore mode when you already have a clear, approved change proposal and just need to execute tasks. It is designed for open-ended investigation, so using it for straightforward implementation work adds unnecessary deliberation.