ticket

Fetch Linear or TICKET.md ticket details and generate an implementation plan.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/amotion-ai/botassist --skill ticket-amotion-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/amotion-ai/botassist/tree/main/.claude/skills/ticket
Command: npx skills add https://github.com/amotion-ai/botassist --skill ticket-amotion-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers waste time manually retrieving ticket details, interpreting requirements, and creating feature branches, leading to inconsistent processes and delays.

Core Features & Use Cases

  • Fetch ticket information from Linear or a local TICKET.md file.
  • Analyze requirements, generate a clear implementation plan, and assess scope.
  • Branch creation with proper naming and status update in Linear.
  • Use case: A developer says “work on BSW-123”, and the skill provides the ticket summary, outlines the steps, and sets up a ready‑to‑code branch.

Quick Start

Invoke the ticket skill with /ticket BSW-123 to fetch the issue, plan the work, and create a branch.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I automate fetching Linear tickets and creating a git feature branch?

To automate fetching Linear tickets and creating a git branch, invoke the ticket skill with an issue ID like BSW-123. It retrieves the ticket details, generates an implementation plan, and automatically creates a properly named feature branch for development.

Can I generate a development plan from a local ticket file instead of Linear?

Yes, you can generate a development plan from a local ticket file by using a TICKET.md file. The skill analyzes the local file's requirements, outlines the necessary implementation steps, and sets up a ready-to-code git branch.

What's the best way to turn Linear issue requirements into an implementation plan?

The best way to turn Linear issue requirements into an implementation plan is using an automation skill that fetches the ticket details, analyzes the scope, and outlines a clear step-by-step development workflow before you start coding.

Do I need to manually update my Linear ticket status when creating a branch?

No, you do not need to manually update your Linear ticket status. The automation workflow handles status updates in Linear automatically as part of the branch creation process after fetching and planning the ticket.

Does the ticket automation workflow work without external dependencies?

Yes, the ticket automation workflow works without external dependencies. It uses built-in Bash commands, API calls, and git operations to retrieve data, analyze code requirements, and create feature branches directly.