What problem does it solve?
Turning a raw GitHub issue or idea into a well-defined unit of work is error-prone: reporter claims go unverified, user experience expectations get lost, and planning starts without knowing what "done" means. This Skill bridges triage and development planning by producing a structured goals document that captures the what and why before anyone decides how.
Core Features & Use Cases
- Claim Verification: Checks every verifiable claim in an issue against the actual codebase (commands, settings, UI elements, error messages) and buckets results as confirmed, disputed, or unverifiable.
- Investigation Import: Automatically detects and imports findings from prior investigation reports instead of re-doing root cause analysis, and recommends running investigation first when a bug lacks one.
- UX and Code Landscape Mapping: Documents triggers, expected flows, edge cases, entry points, affected paths, and risk areas so downstream planning has concrete anchors.
- Use Case: Run it on issue #5096 about missing commit graph branch labels; it fetches the issue via the GitHub CLI, verifies the claims against the source, maps the user experience, and writes
.work/dev/5096/goals.md with testable success criteria and a confidence assessment ready for deep planning.
Quick Start
Ask the AI to scope GitHub issue 5096 into a goals document using the dev-scope skill.