skills.rest
MaxWolf-01
MaxWolf-01COMMUNITY
Explore all skills by this author →
Website𝕏@MaxWolf_01GitHub

tracker

Manages markdown-based ticket tracking with status workflows, dependency graphs, and an HTML board.

3|Updated Jan 10, 2026
Search Tags:#markdown#issue tracker#agent workflow#git worktree#dependency graph#ticket tracking#board
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill tracker-maxwolf-01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tracker
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/tracker
Command: npx skills add https://github.com/MaxWolf-01/agents --skill tracker-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tyro, pyyaml, markdown.

What problem does it solve? Coordinating multi-session agent work requires a persistent record of what is planned, blocked, in review, and done; this Skill defines the conventions for markdown-file tickets and specs so any session can publish, fetch, claim, and retire work without losing provenance or dependency context. ## Core Features & Use Cases - Markdown ticket conventions: Defines where specs and tickets live (agent/tickets/), their frontmatter state machine (proposed, open, claimed, review, done), blocking edges, and decision-ticket types (research, prototype, grilling, legwork). - Board rendering: Ships a board script that renders the whole tracker as one self-contained HTML page with tickets grouped by state, a dependency graph, needs-human queues, and links to diff review pages and GitHub references. - Multi-checkout awareness: Reads in-flight feature state from git worktrees so claims and review flips appear on the board while a feature branch is still unmerged. - Use Case: An orchestrating agent files a proposed ticket from a worker's closing comment, a later session picks it from the frontier, and the human runs the board to see what needs review and rule on it. ## Quick Start Ask the agent to publish the current plan as tickets to the issue tracker and render the board so you can review the frontier.

Frequently Asked Questions about tracker

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

FAQPage Schema
How do I track agent work with markdown tickets?▼

Store tickets as markdown files under agent/tickets with YAML frontmatter declaring status, optional type, and blocked-by edges. Feature work gets a directory with a spec.md and numbered tickets; standalone work is a single file at the tracker root.

How do I render an HTML board from markdown tickets?▼

Run the board script from anywhere in the repo; it finds the nearest agent/tickets directory, renders one self-contained HTML page grouped by state, opens it in a browser, and re-renders on changes until interrupted.

What ticket statuses does the tracker support?▼

Tickets declare proposed, open, claimed, review, or done; blocked is derived when an open ticket's blockers are not done. Proposed means an agent filed it and the user has not ruled; review means finished work awaiting the user's ruling.

Does the board work with git worktrees and feature branches?▼

Yes. The board reads an in-flight feature's tickets from its worktree on the matching branch, shows standalone tickets a branch added, and ignores worktrees whose branches have already merged into the main checkout.

What is a decision ticket and when should I use one?▼

A decision ticket is a ticket whose deliverable is an answer, carrying a type of research, prototype, grilling, or legwork. Use it when a question can be stated sharply but its answer is missing; build tickets that need the answer name it in blocked-by.

Related Skills

Explore More Software Engineering Skills→
AntonBespalovAntonBespalov

system-design-interrogation

Elicit ambiguous system requirements through iterative one-question-at-a-time Spec sessions.

Community
Advanced
nand1234nand1234

merge-to-cp

Merge approved tickets into the CP branch after validation.

Community
Advanced
Obsidian-OwlObsidian-Owl
4

speckit-clarify

Resolve feature specification ambiguities through guided questions and recorded clarifications.

Official
Advanced
mikalvmikalv

project-management

Orchestrates TPM workflows for cycle planning, issue audits, roadmap planning, and research decomposition.

Community
Advanced