Scaffold a new Go project with a Makefile, golangci-lint, GitHub Actions CI, and two-layer git hooks (pre-commit + pre-push). Use when the user says "set up a new Go project", "scaffold a Go project", "create a new Go CLI", or similar.
Scaffold a new SvelteKit project with Biome, Prettier, Vitest, and GitHub Actions CI. Use when the user says "set up a new JS project", "scaffold a SvelteKit project", "create a new frontend app", or similar.
Scaffold a new Python project with uv, ruff, pytest, and GitHub Actions CI. Use when the user says "set up a new Python project", "scaffold a project", "create a new Python app", or similar.
Report a consistent status snapshot for an in-flight /run-epic, /fix-tickets, or DAG variant — the epic/batch progress, every ticket and its state, every agent and what it's doing, and any interesting events from the run so far. Use when the user asks "what's the status", "how's the run going", "what are the agents…
Triage, filter, and sort tk tickets for review. Use when the user asks to review open tickets, sort by priority/type/confidence, triage a backlog, go through P2 bugs, or any similar ticket review workflow. Always use tk triage instead of inline Python/jq for filtering and sorting.
Ship a completed /run-tickets, /run-epic or /fix-tickets batch: merge the integration branch to main, prune worktrees, move leftover non-blocking findings to the repo's backlog epic, close the epic with a ship note, and report remaining work. Use only when the user types /wrap-epic.
Implements one tk ticket inside a /run-tickets workflow. Works in the worktree and branch its prompt names, writes code and tests, commits, and returns a structured result. Also handles rework rounds (AC failures, review findings, merge conflicts) as a fresh agent on the existing branch.
Adversarial review of one ticket's diff inside a /run-tickets workflow, after AC verification. Covers correctness, design fitness, test strength, security, reliability, performance, and conventions. Returns inline rework findings as structured output and files out-of-scope findings as tk tickets.
Checks one ticket's implementation against its acceptance criteria inside a /run-tickets workflow. Binary PASS/FAIL per criterion, backed by quoted code and test assertions, recorded as a note on the ticket and returned as structured output. Does not judge code quality.
Analyze archived /run-tickets runs to find what to tune: rework and block rates, token cost, and escaped defects, broken down by effort policy, implementation and review effort, diff size, and dependents. Read-only; recommends changes with the evidence and sample size behind each. Use when the user asks how…
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires…
Ticket-by-ticket status of a /run-tickets workflow run, running or finished: what each ticket is doing or how it ended, how long each step took, rework and conflict counts, findings filed, merges, and the integration check. Read-only. Use when the user asks how a /run-tickets run is going or went, how long it took…
Implement a set of tk tickets (an epic's children or an explicit list) in parallel using the run-tickets workflow: decisions put to the owner before dispatch, pooled worktrees, one fresh implementer per ticket, AC verification when the ticket has acceptance criteria, adversarial quality review, and gated one-at-a-time…
★not rated 5
changed 5d agoA85 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: