openspec-explore

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

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

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 mode that helps you explore ideas, investigate codebases, compare options, and capture decisions as OpenSpec change artifacts before writing any code. ## Core Features & Use Cases - Exploration Mode: Acts as a curious thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without rushing to implementation. - Codebase Investigation: Reads files, maps architecture, and grounds discussions in the actual code using read-only openspec CLI commands. - ASCII Visualization: Draws plain-ASCII diagrams, state machines, and comparison tables to clarify complex problems. - OpenSpec Integration: Scaffolds new changes via openspec new change, reads artifact status, and captures decisions into proposals, designs, specs, and tasks with explicit user confirmation. - Use Case: Before building a real-time collaboration feature, use this Skill to map the collaboration spectrum, compare CRDT versus presence approaches against your codebase, then capture the chosen direction as an OpenSpec change proposal. ## Quick Start Ask the AI to enter explore mode and help you think through a feature idea or investigate a problem in your codebase 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?

Invoke explore mode and describe your idea in natural language. The Skill investigates your codebase, asks clarifying questions, draws ASCII diagrams, and offers to capture crystallized decisions as an OpenSpec change proposal when you are ready.

What is OpenSpec explore mode used for?

Explore mode is a thinking stance for investigating problems and clarifying requirements without implementing anything. It can read code and run read-only openspec commands, but never writes code; it only creates or updates OpenSpec change artifacts after explicit user confirmation.

Does openspec-explore require the openspec CLI?

Yes, the Skill requires the openspec CLI to be installed. It uses commands like openspec list, status, instructions, and new change to inspect existing changes and scaffold new ones with proper metadata.

Can explore mode write code or implement features?

No, explore mode never writes code or implements features. It may only create or update OpenSpec change artifacts such as proposals, designs, and specs within a scope you explicitly confirm, and it asks before any write-capable action.

How do I capture exploration decisions into a change proposal?

Tell the Skill you want to capture the exploration as a change. It runs openspec new change to scaffold the change, then follows status and instructions output to create requested artifacts like proposal.md, design.md, and specs in dependency order.

When should I not use explore mode?

Avoid explore mode when you already know exactly what to build and want immediate implementation. It is designed for open-ended thinking, so for direct coding tasks you should exit explore mode and create a change proposal first.