Dev10x:ticket-scope

Automate Linear ticket scoping with context gathering, research, and story point estimation.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-ticket-scope-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:ticket-scope
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/ticket-scope
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-ticket-scope-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__claude_ai_Linear__get_issue, mcp__claude_ai_Linear__list_issues, mcp__claude_ai_Linear__list_comments, mcp__claude_ai_Linear__save_comment, Skill(Dev10x:jtbd), Agent, WebFetch, Grep, Glob, Read, Bash(mkdir -p:*), AskUserQuestion, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of scoping Linear tickets, providing a comprehensive approach to technical research, architecture design, and acceptance criteria formatting, thereby enhancing the efficiency of the development process.

Core Features & Use Cases

  • Ticket Scoping: Gather ticket context, conduct technical research, and design solutions.
  • Story Point Estimation: Estimate complexity and draft Job Stories using the JTBD framework.
  • Acceptance Criteria Formatting: Create detailed technical scoping documents with clear objectives, architecture, and implementation steps.
  • Use Case: A developer preparing to implement a Linear ticket uses this Skill to gather context, conduct research, and design a solution before coding, ensuring a clear and well-understood approach.

Quick Start

Use the /Dev10x:ticket-scope command followed by the ticket ID, e.g., /Dev10x:ticket-scope PAY-329.

Frequently Asked Questions about Dev10x:ticket-scope

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

FAQPage Schema
How do I scope Linear tickets with precise acceptance criteria and story point estimation?

Scoping Linear tickets involves gathering context, conducting technical research, and designing solutions to generate clear acceptance criteria and story point estimates. This process ensures developers have a well-understood technical plan before coding begins.

What is the best way to write acceptance criteria for a technical scoping document?

Formatting acceptance criteria requires creating detailed technical scoping documents with clear objectives, architecture, and implementation steps. This ensures the development team understands the exact requirements and technical design before implementation.

How do I estimate story points using the JTBD framework for software engineering tasks?

Story point estimation using the JTBD framework involves drafting Job Stories to assess complexity and define the job-to-be-done. This approach clarifies user needs and technical scope, leading to more accurate complexity estimates for development tickets.

Can I automatically gather context and comments from a Linear ticket for technical research?

Yes, ticket context gathering automates retrieving Linear issues and comments to inform technical research. This integration pulls existing ticket data directly to provide the necessary background for architecture design and solution planning.

Do I need a specific Linear ticket ID to start the technical scoping process?

Yes, providing a Linear ticket ID is required to initiate the scoping process. The command uses this identifier to fetch the specific issue details and comments needed to conduct technical research and design the solution.

Why should I use an automated ticket scoping tool instead of manually researching a Linear issue?

Automated ticket scoping streamlines context gathering, technical research, and architecture design into a comprehensive workflow. This enhances development efficiency by producing structured implementation steps and reducing manual planning overhead.