dev-scope

Generates goals documents from GitHub issues to scope development work before planning.

9.9k|1.8k|Updated Aug 8, 2016
One-click install
npx skills add https://github.com/gitkraken/vscode-gitlens --skill dev-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-scope
Source: https://github.com/gitkraken/vscode-gitlens/tree/main/.claude/skills/dev-scope
Command: npx skills add https://github.com/gitkraken/vscode-gitlens --skill dev-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about dev-scope

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scope a GitHub issue before planning development work?

Invoke the skill with the issue number, for example /dev-scope 5096. It fetches the issue with the GitHub CLI, verifies claims against the codebase, maps user experience and code landscape, and writes a goals.md file to .work/dev/<number>/.

How to scope a feature idea that has no GitHub issue?

Pass a quoted description instead of an issue number, such as /dev-scope "add natural language search". The skill creates a slug-based dev folder and treats the description as the entire input, skipping issue fetching.

Does dev-scope require an investigation report for bugs?

No, but it checks for one. If a bug has a matching investigation report, it imports root cause, affected files, and effort estimates. If none exists, it pauses and recommends running /investigate first, letting you choose to proceed without it.

Can dev-scope handle multiple issues at once?

Yes. Pass multiple issue numbers and it processes each independently, producing one goals.md per issue in separate dev folders, then presents a summary of all generated files.

What are the limitations of dev-scope?

It deliberately stays in the what and why, never producing implementation plans or re-running investigations. Claim verification is lightweight, so intermittent or environment-specific issues may be marked unverifiable rather than resolved.