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.
npx skills add majiayu000/claude-skill-registry --skill openspec-explore-durandom-layton --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes. **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 - **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 - **Grounded** - Explore the actual codebase when relevant, don't just theorize --- ## What You Might Do Depending on what the user brings, you might: **Explore the problem space** - Ask clarifying questions that emerge from what they said - Challenge assumptions - Reframe the problem - Find analogies **Investigate the codebase** - Map existing architecture relevant to the discussion - Find integration points - Identify patterns already in use - Surface hidden complexity **Compare options** - Brainstorm multiple approaches - Build comparison tables - Sketch tradeoffs - Recommend a path (if a
- The Stance
- What You Might Do
- OpenSpec Awareness
- Check for context
- When no change exists
- When a change exists
- What You Don't Have To Do
- Handling Different Entry Points
- Ending Discovery
- Guardrails
openspec list --json
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 majiayu000/claude-skill-registry --skill openspec-explore-durandom-layton --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 majiayu000/claude-skill-registry, a repository with 534 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.