ticket-flow

A ticket-management workflow for Claude Code that connects tickets to Git worktrees, which are separate working folders for Git branches. It guides work through specification, pickup, implementation, and completion stages.

In plain words
What is it for?
Use it to organize coding tickets, create isolated workspaces, implement several tickets, and finish completed work through a consistent command flow.
Why use it?
It keeps ticket work separated and gives teams a defined path from an idea to finished code, including options for local or parallel work.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add keefar/ticket-flow
agentmods
npx agentmods add plugins/keefar/ticket-flow/marketplace
Clone the repo
git clone --depth 1 https://github.com/keefar/ticket-flow

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ticket-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/marketplace.json · 14 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "ticket-flow",
  "description": "Kanban- or beads-backed git-worktree ticket workflow plugin for Claude Code.",
  "owner": { "name": "Christoph Schmid" },
  "plugins": [
    {
      "name": "ticket-flow",
      "description": "Kanban- or beads-backed ticket workflow for Claude Code: /spec → /pickup → /implement → /finish, orchestrated by /flow (--local, --parallel, --spawn), each ticket in its own git worktree.",
      "source": "./"
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 14 lines scan A 4278f8a0bdc3

Subscribe to this mod's changes

ticket-flow is a plugin published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.