explore

Explore ideas and clarify requirements through open-ended questioning and ASCII diagrams.

15|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/v0lka/skills --skill explore-v0lka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/v0lka/skills/tree/main/research/explore
Command: npx skills add https://github.com/v0lka/skills --skill explore-v0lka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to act as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use it when requirements are unclear or when discussing architecture and design decisions; it helps you think deeply without implementing changes.

Core Features & Use Cases

  • Curious, non-prescriptive thinking partner that surfaces multiple directions, asks clarifying questions, and surfaces tradeoffs.
  • Visualizes ideas with ASCII diagrams and grounded references to the codebase, surfacing risks and unknowns to inform decisions.
  • Supports a transition to Plan Mode when ideas crystallize, and enforces guardrails that keep conversations productive and safe.

Quick Start

Ask me to begin exploring a problem by outlining goals, questions, and potential approaches.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I clarify unclear product requirements before starting implementation?

To explore ideas and clarify requirements, engage a non-prescriptive thinking partner that asks clarifying questions and surfaces multiple directions. This method helps you frame strategy and investigate problems across product, software architecture, and research contexts without writing code.

What is the best way to visualize software architecture during early design discussions?

The best way to visualize software architecture during early design is by generating ASCII diagrams. This allows you to map ideas, surface risks and unknowns, and ground references to the codebase to inform your architecture decisions effectively.

Can I use this ideation mode to write and execute code automatically?

No, you cannot use this ideation mode to execute code. It enforces strict guardrails to prevent code execution, providing a non-implementation thinking mode strictly for exploring ideas, investigating problems, and discussing architecture.

How do I transition from exploring ideas to creating a concrete plan?

To transition from exploring ideas to creating a concrete plan, trigger the optional Plan Mode. Once your early design discussions and requirements crystallize, this mode maps your crystallized ideas directly into actionable architectural plans.

Does this thinking partner approach work for research strategy framing?

Yes, this thinking partner approach works for research strategy framing. It acts as a curious, non-prescriptive assistant that helps you investigate problems, ask clarifying questions, and explore multiple directions without implementing changes.