Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements.
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to explore refactoring our logging module. Before we discuss solutions, what initial CLI inspection should be run to see existing active OpenSpec changes?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running openspec list --json to inspect active context. | Missed | Passed |
The instructions your model reads when the skill loads.
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 (e.g., start a change with /opsx:new or /opsx:ff). 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.
Depending on what the user brings, you might:
Explore the problem space
Investigate the codebase
Compare options
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.