source-command-opsx-explore

Guides open-ended exploration of ideas, problems, and requirements within OpenSpec workflows.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-explore-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-explore
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/source-command-opsx-explore
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-explore-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem. This Skill provides a structured thinking partner mode for investigating ideas, clarifying requirements, and exploring a codebase before committing to a change proposal. ## Core Features & Use Cases - Explore Mode Stance: Enforces a no-implementation mindset where the AI investigates, questions assumptions, and visualizes concepts with ASCII diagrams instead of writing code. - OpenSpec Integration: Checks active changes via openspec list --json, reads existing proposals, designs, and specs, and offers to capture decisions into the right artifacts. - Codebase Grounding: Maps existing architecture, finds integration points, and surfaces hidden complexity relevant to the discussion. - Use Case: A developer is unsure whether to use PostgreSQL or SQLite for a new feature. They invoke explore mode to compare tradeoffs, inspect the current data layer, and optionally capture the final decision in design.md. ## Quick Start Ask the AI to enter explore mode with a topic such as "explore whether the auth system should be refactored" and let it investigate the codebase and discuss options.

Frequently Asked Questions about source-command-opsx-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore a software idea before writing code?

Invoke explore mode with your topic, such as a vague idea, a specific problem, or a change name. The AI investigates the codebase, asks clarifying questions, compares options, and visualizes concepts without implementing anything.

What is OpenSpec explore mode used for?

Explore mode is a thinking stance for investigating problems and clarifying requirements before creating change proposals. It can read OpenSpec artifacts for context and offer to capture decisions into specs, design.md, or proposal.md.

Can explore mode write code or implement features?

No. Explore mode explicitly forbids writing application code or implementing features. It may only read files, search code, and create OpenSpec artifacts like proposals and specs when the user asks.

Does explore mode require the openspec CLI?

The openspec CLI is used to check active changes with openspec list and read change status, but exploration itself works without it. OpenSpec integration adds context when a project uses spec-driven development.

When should I exit explore mode and create a change proposal?

Exit explore mode when the problem shape is clear and decisions have crystallized. The AI will offer to create a change proposal or update artifacts, but the user decides when to formalize.