Agent skill

openspec-explore

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

VILA-Labgithub.com/VILA-LabGitHub ↗
claude-codecodex
Install
npx skills add VILA-Lab/FigMirror --skill openspec-explore --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.0
Declared author: openspec
Requires: Requires openspec CLI.
Path: .claude/skills/openspec-explore/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 497
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

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. --- ## The Stance - **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script - **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions. - **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking - **Adaptive** - Follow interesting threads, pivot when new information emerges - **Patient** - Don't rush to conclusions, let the shape of the problem emerge - **Gr

What's inside
Steps it walks through
  1. The Stance
  2. What You Might Do
  3. OpenSpec Awareness
  4. Check for context
  5. When no change exists
  6. When a change exists
  7. What You Don't Have To Do
  8. Handling Different Entry Points
  9. Ending Discovery
  10. Guardrails
Commands it runs
openspec list --json
More from FigMirror
All skills →
About this skill
What does the openspec-explore skill do?

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

How do I install it?

Run `npx skills add VILA-Lab/FigMirror --skill openspec-explore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From VILA-Lab/FigMirror, a repository with 497 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going