Openspec Explore

This is basically a "thinking mode" for Claude that stops it from jumping straight to implementation. It encourages asking questions, drawing ASCII diagrams to visualize problems, and exploring multiple angles before committing to code. The core rule is simple: read files and investigate all you want, but don't write code. If you try to implement something, Claude reminds you to exit explore mode first. It's aware of OpenSpec artifacts, so it can read your existing proposals and designs to ground the conversation, and it'll offer to capture decisions when they crystallize. Nice for when you need to think through architecture or clarify requirements without Claude auto-generating solutions.

GitHub stars: 457
last updated: May 25, 2026

View on GitHub

Install

$ npx -y skills add vila-lab/figmirror --skill openspec-explore --agent claude-code

Installs into .claude/skills of the current project.

Files

Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.

IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.

This is a stance, not a workflow. There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.