ticket

Manage tasks and dependencies in Git-friendly Markdown ticket stores.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/snqb/my-skills --skill ticket-snqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/snqb/my-skills/tree/main/ticket
Command: npx skills add https://github.com/snqb/my-skills --skill ticket-snqb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps tasks and their dependencies in a portable, version-controlled format by storing them as Markdown files in a local Git repository, enabling persistent memory across sessions and human-agent collaboration without external services.

Core Features & Use Cases

  • Local-first, git-native task storage using Markdown files in .tickets and .tickets-done for completed work.
  • Dependency-aware planning with commands to link tasks (tk dep), view readiness (tk ready), and visualize a dependency graph (tk dep tree).
  • Lifecycle management with create, status, show, edit, and close operations to track progress from todo to done.
  • Lightweight collaboration and auditability through plain-text tickets that can be reviewed with standard Git workflows.

Quick Start

Initialize the tracker with tk init, then create a ticket with tk create, and start linking tasks with tk dep.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I track tasks and dependencies using Markdown in a Git repository?

Track tasks and dependencies using Markdown by storing tickets in local Git directories, enabling version-controlled task management and persistent state across sessions without external databases.

What is the best way to manage task dependencies for local-first workflows?

Manage task dependencies for local-first workflows by linking tickets with explicit dependency commands, checking readiness, and visualizing dependency trees to orchestrate complex work directly within your repository.

Can I use Git workflows to collaborate on task tracking without external services?

Yes, you can collaborate on task tracking without external services by using plain-text Markdown tickets that integrate natively with standard Git workflows for lightweight review and auditability.

How do I initialize and create tickets for task management in Markdown?

Initialize the tracker with a single command, then create tickets as Markdown files to start managing your tasks, linking them together with dependency commands to visualize project readiness.

Does this Markdown task tracker persist state across different sessions?

The Markdown task tracker persists state across sessions by saving all ticket data and dependency links as files in a local Git repository, ensuring work is never lost between closures.