explore-mode

Clarify problems and surface exploration options with trade-offs without modifying code.

Updated Sep 30, 2021
One-click install
npx skills add https://github.com/isymchych/accel-os --skill explore-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-mode
Source: https://github.com/isymchych/accel-os/tree/main/ai/codex/skills/explore-mode
Command: npx skills add https://github.com/isymchych/accel-os --skill explore-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery-first collaboration mode for clarifying problems, inspecting repo/environment state, and surfacing options with trade-offs without implementing. Use when the user asks to explore, investigate, analyze, compare approaches, de-risk a direction, or gather context before planning/execution. Also use when uncertainty is high and the user is not yet decision-complete.

Core Features & Use Cases

  • Clarify problems and options without implementing code or mutating tracked repo state.
  • Enforce a safe exploration loop that classifies commands by repo/environment impact and surfaces 2-4 branches before convergence.
  • Support explicit mode switching and capture workflows to prevent unintended persistence or mutations.

Quick Start

Describe the current problem and surface 2–4 safe exploration options without changing any files.

Frequently Asked Questions about explore-mode

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

FAQPage Schema
How do I analyze a repository and compare approaches before writing any code?

To analyze a repository and compare approaches before coding, you need a discovery-first workflow that inspects repo state and surfaces 2-4 safe exploration branches with explicit trade-offs while enforcing non-mutating behavior to prevent unintended changes.

What is the best way to investigate a codebase when uncertainty is high?

The best way to investigate a codebase with high uncertainty is to use a safe exploration loop that classifies commands by repo impact, surfaces options with trade-offs, and captures workflows using explicit mode-switching to prevent unintended persistence or mutations.

How do I start clarifying a problem and de-risking a direction in my environment?

You start clarifying a problem and de-risking a direction by describing the current problem and requesting 2-4 safe exploration options, which allows you to gather context and evaluate trade-offs without implementing code or mutating tracked repo state.

Does this exploration approach support safe mode-switching during repo inspection?

Yes, this exploration approach supports safe mode-switching during repo inspection by enforcing guarded transitions and classifying commands by environment impact, ensuring that all investigation and analysis remains non-mutating and prevents unintended persistence.

When should I avoid using an explore mode for problem-analysis?

You should avoid using explore mode for problem-analysis when you are already decision-complete and ready for implementation, as it is designed strictly for gathering context, clarifying problems, and comparing approaches without writing code or mutating files.