Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".
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, investigate the codebase, and run read-only commands or tools without confirmation, but you must NEVER write code or implement features. If the user asks you to implement something, do not start it here: say that explore mode does not implement, and point them at `/opsx-propose`, which turns the discussion into a change. The work happens from that change, never from explore mode. You MAY create or update OpenSpec change artifacts (proposals, designs, specs) within a confirmed scope—that's capturing thinking, not implementing. Answering design or clarifying questions is never consent to write. Before the first write-capable action, name the artifacts or files you would change and what you would do, ask a direct yes/no question, and wait for the user's confirmation in a separate message. Confirmation covers only the scope you described; ask again before expanding it. An explicit request from the user to capture the exploration as a new change is itself that confirmation, covering the change and…
…
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_szzrsbm6kk37xub7
GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/openspec-explore
GET https://markdownregistry.com/api/v1/blob/2be39a28c09c4aeb6715ea858efb1261f3dc65445e849bb18befe986f9ffba38
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.
intent-driven-dev/intent-driven-template · .agents/skills/acceptance-test-authoring/SKILL.md · Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step…
intent-driven-dev/intent-driven-template · .agents/skills/c4-diagrams/SKILL.md · Use when explaining existing code architecture, visualizing a new system before detailed design, mapping software…
intent-driven-dev/intent-driven-template · .agents/skills/grill-me/SKILL.md · Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of…
intent-driven-dev/intent-driven-template · .agents/skills/openspec-git-discipline/SKILL.md · Use when running OpenSpec propose, continue, apply, verify, archive, or worktree workflows where proposal artifacts…
intent-driven-dev/intent-driven-template · .agents/skills/spec-as-source/SKILL.md · Use when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable…
intent-driven-dev/intent-driven-template · .agents/skills/test-driven-development/SKILL.md · Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
intent-driven-dev/intent-driven-template · .opencode/skills/adversarial-authoring/SKILL.md · Use when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…
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…