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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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.
---
## 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
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_jtv6ui4yoto3n5ye
GET https://markdownregistry.com/api/v1/resolve?ref=justinjdev/fellowship/openspec-explore
GET https://markdownregistry.com/api/v1/blob/64ded43c11f45d9be10670202659bbbb81bb70e4fd67d3579ae31f1a1f693911
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
justinjdev/fellowship · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
justinjdev/fellowship · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
justinjdev/fellowship · .claude/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
justinjdev/fellowship · .claude/skills/openspec-continue-change/SKILL.md · Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change…
justinjdev/fellowship · .claude/skills/openspec-ff-change/SKILL.md · Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for…
justinjdev/fellowship · .claude/skills/openspec-new-change/SKILL.md · Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature…
justinjdev/fellowship · .claude/skills/openspec-onboard/SKILL.md · Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
justinjdev/fellowship · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
justinjdev/fellowship · .claude/skills/openspec-verify-change/SKILL.md · Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete…
justinjdev/fellowship · plugin/skills/council/SKILL.md · Invoke when the user runs /council or from /scout. Quest inlines this orientation as its Research step 2 and does not…
monid-ai/monid · .opencode/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
fengshao1227/ccg-workflow · .agents/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
mememeow-studio/mememeow · .agents/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
mememeow-studio/mememeow · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
mememeow-studio/mememeow · .opencode/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
partcad/partcad · .cursor/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
partcad/partcad · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
asymmetric-al/core · .agents/skills/openspec-explore/SKILL.md · Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying…
