What problem does it solve? Researching a GitHub issue before planning often turns into an unbounded repository tour or a mandatory multi-agent pipeline that wastes time. This Skill answers the few technical questions blocking a concrete plan, verifies claims directly in source, and publishes a compact, hash-pinned research record. ## Core Features & Use Cases - Bounded Investigation: Targets 2-4 minutes for small tasks, tracing entry point to logic to persistence instead of scanning whole files or historical documents. - Scoped Delegation: Uses codebase-locator, codebase-pattern-finder, or codebase-analyzer only when genuinely needed, with zero to two specialists and no mandatory Locate-Patterns-Analyze pipeline. - Source-Pinned Records: Publishes a v2 Research record via handoff.py with stable fact IDs, 5-10 decisive source locations, and file hashes bound by the helper. - Use Case: Given a GitHub issue URL, run /research to produce a verified evidence record with test prerequisites and open questions, then hand off to /plan with the exact comment URL. ## Quick Start Run /research on this GitHub issue URL to produce a bounded, source-verified research record ready for the planning stage.
