What problem does it solve? It prevents unstructured, memory-based answers by enforcing a strict research workflow where every claim is backed by cited evidence from code, docs, config, or external sources, with human approval gates at each stage. ## Core Features & Use Cases - Structured Research Workflow: Classifies requests as internal, external, or mixed, then runs planning, gathering, verification, and synthesis as separate gated phases. - Human Approval Checkpoints: Stops for scope, source, and synthesis approval unless the user explicitly passes --yolo for full autonomy. - Evidence Discipline: Requires file paths and line numbers for code claims, URLs and quotes for web claims, and records rejected-but-relevant findings. - Use Case: Ask whether the ECommerceApp checkout flow matches the payments lifecycle spec; the skill produces a research plan, gathers cited findings into analysis/findings/, cross-checks code against docs, and writes a verified summary. ## Quick Start Ask the research-gatherer to investigate how coupon apply-revert is implemented in ECommerceApp and approve the scope when prompted.