skills.rest
galz10
galz10COMMUNITY
Explore all skills by this author →
GitHub

ticket-manager

Manage Linear tickets locally as Markdown files with frontmatter.

454|45|Updated Jan 9, 2026
Search Tags:#planning#Linear#PRD#Markdown#tickets#session#local
One-click install
npx skills add https://github.com/galz10/pickle-rick-extension --skill ticket-manager-galz10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-manager
Source: https://github.com/galz10/pickle-rick-extension/tree/main/skills/ticket-manager
Command: npx skills add https://github.com/galz10/pickle-rick-extension --skill ticket-manager-galz10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you manage Linear tickets locally using Markdown files to replace cloud-based workflows, enabling offline work and local organization.

Core Features & Use Cases

  • Ticket creation & updates: Create, modify, search, and break down features into atomic tickets stored as Markdown files in the active session directory.
  • Session-based planning: Use a session root and the WriteTodosTool to track subtasks while working on a ticket.
  • PRD breakdown: Break down PRDs into a hierarchical set of tickets for clearer workflow and traceability.

Quick Start

  • Locate your working session with the get_session.sh script: ~/.gemini/extensions/pickle-rick/scripts/get_session.sh
  • Create a new ticket from ideas or a thoughts document, then update or search existing tickets in the session directory using the described workflows.
  • Optionally link a thoughts document to the new ticket and reference related tickets.

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?▼

Local Linear ticket management uses Markdown files to create, update, and search tickets within a session-based workspace, replacing cloud workflows. It enforces a frontmatter-driven ticket structure for offline organization.

How do I break down a PRD into atomic tickets in a local session?▼

PRD breakdown splits product requirement documents into a hierarchical set of atomic tickets. It integrates with the WriteTodosTool to track subtasks and stores the resulting tickets in the active session directory.

Do I need an active session directory to create and update tickets offline?▼

Yes, ticket creation and updates require an active session directory. You locate your working session using the get_session.sh script before organizing frontmatter-driven Markdown tickets locally.

Can I link a thoughts document to a newly created Markdown ticket?▼

Yes, you can optionally link a thoughts document to a new ticket. This allows you to reference related tickets and maintain local organization when creating tickets from ideas within your session.

What's the best way to organize offline ticketing without relying on cloud-based workflows?▼

Offline ticketing is organized through a session-based workspace using Markdown files. This local approach enforces a frontmatter-driven structure for tracking features and subtasks without cloud dependencies.

Why does my local ticket management require a frontmatter-driven Markdown structure?▼

The frontmatter-driven Markdown structure enforces consistent ticket formatting for local Linear management. This standardization enables reliable searching, updating, and decomposition of PRDs into atomic tickets within the session.

Related Skills

Explore More Product & Management Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
galz10galz10
454

ticket-manager

Manage Linear tickets locally as Markdown files with frontmatter.

Community
Basic
jayhjenkinsjayhjenkins
1

prd-creation

Guide an interactive eight-phase session to create and validate Product Requirements Documents.

Community
Advanced
czh-ee-2023czh-ee-2023

run-experiment

Deploy and execute machine learning experiments across local and remote environments.

Community
Advanced