openspec-explore

Explores ideas and clarifies requirements through OpenSpec change artifacts and codebase investigation.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-explore-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-explore
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-explore-raphaelmans

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 structured thinking partner that investigates the codebase, visualizes options, and captures decisions as OpenSpec change artifacts without writing production code. ## Core Features & Use Cases - Explore Mode Stance: Acts as a curious thinking partner that asks questions, challenges assumptions, and surfaces risks instead of implementing code. - OpenSpec Integration: Reads project context via the openspec CLI, scaffolds new changes with openspec new change, and captures insights into proposals, designs, specs, and tasks. - ASCII Visualization: Draws plain-ASCII diagrams, state machines, and comparison tables to clarify architecture and tradeoffs. - Use Case: A developer unsure whether to use SQLite or Postgres for a CLI tool enters explore mode, gets a grounded comparison based on project constraints, and captures the decision in design.md once confirmed. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem before creating an OpenSpec 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?

Enter explore mode and describe your idea or problem in natural language. The assistant investigates the codebase, draws ASCII diagrams, compares options, and only captures OpenSpec artifacts after you explicitly confirm the scope.

How does OpenSpec capture design decisions during exploration?

Decisions are written to change artifacts such as design.md, proposal.md, specs, or tasks.md depending on the insight type. New changes are scaffolded with the openspec new change CLI command, never created by hand.

Can explore mode write code or implement features?

No. Explore mode is strictly read-only for code and never implements features. It may only create or update OpenSpec change artifacts within a scope you explicitly confirm, and it asks again before expanding that scope.

What is an OpenSpec store and when do I need one?

A store is a standalone OpenSpec repository registered on your machine. When your work lives in one, the assistant discovers store ids with openspec store list and passes --store <id> to commands that read or write specs and changes.

Why does explore mode ask for confirmation before creating artifacts?

Confirmation ensures writes match your intent. Before the first write-capable action, the assistant names the files it would change, asks a direct yes/no question, and waits for your reply in a separate message.