ticket-manager

Manage Linear tickets locally as Markdown files with hierarchical breakdown.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DaRipper91/gemini-termux-migration --skill ticket-manager-daripper91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-manager
Source: https://github.com/DaRipper91/gemini-termux-migration/tree/main/AI_Knowledge_Base/Workflow_and_Project_Management/ticket-manager
Command: npx skills add https://github.com/DaRipper91/gemini-termux-migration --skill ticket-manager-daripper91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows you to manage Linear tickets locally using Markdown files, replacing the need for a cloud-based Linear MCP workflow for creating, updating, and searching tickets.

Core Features & Use Cases

  • Local Ticket Management: Create, update, and search tickets stored as Markdown files within your session directory.
  • Hierarchical Breakdown: Break down large features or PRDs into atomic implementation tickets with clear parent-child relationships.
  • Automated Workflow: Manages ticket status, creation dates, and updates, ensuring consistency.
  • Use Case: When you receive a new feature request, use this Skill to break it down into manageable, actionable tickets, track their progress locally, and ensure all implementation details are captured.

Quick Start

Use the ticket-manager skill to create a new child ticket for the parent ticket located at /path/to/session/linear_ticket_parent.md.

Frequently Asked Questions about ticket-manager

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

FAQPage Schema
How do I manage Linear tickets locally using Markdown files?

You can manage Linear tickets locally by creating, updating, and searching Markdown files stored in a session directory. This replaces cloud-based workflows by tracking ticket status, creation dates, and updates directly on your machine.

What is the best way to break down a large PRD into atomic implementation tickets?

Breaking down large features into atomic implementation tickets is handled through hierarchical Markdown files. This process establishes clear parent-child relationships, ensuring every implementation detail is captured and linked properly within a defined ticket template.

Can I create and track project tasks locally without a cloud-based Linear MCP workflow?

Yes, local ticket management completely replaces the need for a cloud-based Linear MCP workflow. It utilizes a WriteTodosTool for session planning and generates unique IDs for tickets locally, ensuring proper linkage and status updates.

How do I update ticket status and ensure proper parent-child linkage in a local workflow?

Updating ticket status and maintaining parent-child linkage is managed automatically within the local Markdown ticket template. The workflow generates unique IDs for each ticket, ensuring consistent status updates and hierarchical relationships.

Does local ticket management support searching through session directory Markdown files?

Yes, local ticket management supports searching through Markdown files stored in your session directory. You can search for specific tickets, check their current status, and verify hierarchical task breakdowns directly within your local environment.

Why use a local Markdown ticket manager instead of cloud-based project management tools?

A local Markdown ticket manager eliminates cloud dependency by storing session planning data locally. It provides automated workflow management for ticket creation and updates, ensuring consistent tracking of atomic implementation tasks without external network requirements.