What problem does it solve?
Helps teams and individuals enter a disciplined "explore mode" to think through ambiguous requirements, investigate code, and clarify trade-offs before any implementation begins. It prevents premature coding by enforcing a stance of discovery, surfacing unknowns, and reducing verification failures later in the workflow.
Core Features & Use Cases
- Exploratory Stance: Provides a Feynman-first thinking posture that restates requirements simply, surfaces gaps, and forces concrete choices.
- Codebase Investigation: Guides targeted file reads, traces execution paths, and maps integration points without writing or modifying files.
- Structured Decisioning: Always asks concrete A/B/C + Other options, offers recommendations grounded in repository patterns, and drafts verification steps.
- Verification & Guardrails: Includes a Zero-Fog checklist and rules for when to run verification subagents; enforces "no implementation" and safe subagent usage.
- Subagent Coordination: Prepares briefs for specialized subagents (research, docs, UI) and instructs them to report findings only.
Quick Start
Ask the assistant to "Help me explore and map the requirements for <feature> and identify the files and decision points I should investigate next."