reversa-explorer

Generates three to five distinct solution options for a framed problem into options.md.

1.5k|405|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-explorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-explorer
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-explorer
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-explorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When planning a new feature or change, teams often jump to the first idea without exploring alternatives. This Skill forces structured divergence: it generates multiple materially distinct solution paths for a framed problem, including the mandatory "do not build" and "use something off-the-shelf" options, without recommending any of them.

Core Features & Use Cases

  • Divergent Option Generation: Produces 3 to 5 materially distinct options covering different effort levels, always including "do not build" and "use something ready" paths.
  • Structured options.md Output: Writes a standardized Markdown document with effort, legacy impact, reversibility, and core assumptions for each option, all marked with a 🟡 PLANNED seal.
  • Legacy-Aware Analysis: When working on legacy projects, reads existing module documentation so each option states its impact on what already exists.
  • Use Case: After framing a problem with the reversa-framer agent, run this Skill to open the solution space before the Arbiter agent converges on a decision, ensuring no viable path is overlooked.

Quick Start

Ask the agent to generate solution options for the currently framed problem in the active ideation session and write them to options.md.

Frequently Asked Questions about reversa-explorer

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

FAQPage Schema
How do I generate multiple solution options for a software problem?

Run this Skill after framing the problem with the reversa-framer agent. It reads framing.md from the active ideation session and writes 3 to 5 distinct options to options.md, including mandatory "do not build" and "use something ready" paths.

What is the difference between the Explorer and Arbiter agents in Reversa?

The Explorer diverges by generating solution options and is explicitly forbidden from recommending any of them. The Arbiter is a separate agent responsible for convergence and choosing among the options the Explorer produced.

Does the reversa-explorer work with legacy codebases?

Yes. When the ideation context is legacy, the Skill reads existing module documentation in the output folder so each generated option explicitly states its impact on the current system. In greenfield projects it marks legacy impact as none.

Why does the Explorer refuse to recommend the best option?

Recommendation is intentionally prohibited by design to prevent anchoring bias during divergence. Ranking and selection are the responsibility of the reversa-arbiter agent in a later stage of the ideation workflow.

What happens if options.md already exists in the session?

The Skill asks for explicit confirmation before overwriting. Without an explicit "yes", it stops without writing anything, preserving the existing options document.