source-command-opsx-explore

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

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-explore-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-opsx-explore
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.agents/skills/source-command-opsx-explore
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-explore-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned requirements. This Skill provides a structured thinking mode where you can investigate ideas, map the codebase, and compare options without writing any application code. ## Core Features & Use Cases - Explore Mode Stance: Enforces a thinking-only mode where the AI reads files, searches code, and investigates the codebase but never implements features. - OpenSpec Integration: Checks active changes via openspec list --json, reads existing proposals, designs, and specs, and offers to capture decisions into the right artifacts. - Visualization Support: Encourages ASCII diagrams, comparison tables, state machines, and architecture sketches to clarify thinking. - Use Case: Before building a new authentication system, enter explore mode to map the current auth flow, compare session-based versus token-based approaches, and capture the final decision in design.md. ## Quick Start Ask the AI to enter explore mode and think through how the current supplier order flow could support multiple suppliers.

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 problem before writing code with OpenSpec?▼

Enter explore mode and describe the idea, problem, or change name you want to think through. The AI investigates the codebase, asks clarifying questions, and visualizes options, but never writes application code during exploration.

What is explore mode in a spec-driven development workflow?▼

Explore mode is a thinking stance, not a fixed workflow. It lets you read files, map architecture, compare approaches, and surface risks freely, with no required steps or mandatory outputs before formalizing a change proposal.

Can explore mode create or update OpenSpec artifacts?▼

Yes, explore mode may create or update OpenSpec artifacts such as proposals, designs, specs, and tasks when you ask, since that captures thinking rather than implementing code. It offers to capture decisions but never does so automatically.

Can I implement features while in explore mode?▼

No, explore mode explicitly forbids writing application code or implementing features. If you ask for implementation, the AI reminds you to exit explore mode and create a change proposal first.

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

Exit explore mode when your thinking has crystallized into a concrete scope, requirements, or design direction. The AI typically offers to create a proposal once insights feel solid enough to formalize.