Warcraft Exploring

Overview

Exploring is the decision-extraction phase. Before any research or planning, you must understand what the user actually wants — including the parts they haven't thought about yet.

Core principle: Every ambiguity resolved here saves 10x rework downstream.

The output is a CONTEXT.md file that becomes the single source of truth for all downstream skills (planning, validating, executing, reviewing).

When to Use

• A new feature request arrives (routed from beo/router)
• The request is classified as standard or unclear complexity
• Before any planning or implementation work
• When the user says "build", "add", "change", "implement", "design"

When NOT to Use