ticket-to-pr

ticket-to-pr is a plugin for Claude Code from benjaminthomas/spec-driven-dev. Its manifest loads nothing; the 9 skills it bundles cost 1,462 tokens per session together, scanned A, original, MIT.

A step-by-step workflow for taking a software ticket from investigation and specification through implementation, verification, review, and release. It also includes guidance for SEO, which is the practice of helping web content appear in search results, and GEO, guidance for visibility in AI-generated answers.

In plain words
What is it for?
Use it to investigate tickets, write specifications, build features in batches, verify and review changes, create checkpoints, and prepare them for release.
Why use it?
It gives a coding project a defined path from request to pull request, so requirements and checks are less likely to be skipped. The SEO and GEO guidance addresses discoverability alongside code work.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions .claude-plugin.

Good fit Use it to investigate tickets, write specifications, build features in batches, verify and review changes, create checkpoints, and prepare them for release.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add benjaminthomas/spec-driven-dev
/plugin install ticket-to-pr
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.

Clone the repo
git clone --depth 1 https://github.com/benjaminthomas/spec-driven-dev

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ticket-to-pr

README.md
[![agentmods](https://agentmods.dev/badge/plugins/benjaminthomas/spec-driven-dev/plugin/github.svg)](https://agentmods.dev/plugins/benjaminthomas/spec-driven-dev/plugin)
Your own site
<a href="https://agentmods.dev/plugins/benjaminthomas/spec-driven-dev/plugin"><img src="https://agentmods.dev/badge/plugins/benjaminthomas/spec-driven-dev/plugin/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ticket-to-pr

Your own site · 80×15
<a href="https://agentmods.dev/plugins/benjaminthomas/spec-driven-dev/plugin"><img src="https://agentmods.dev/badge/plugins/benjaminthomas/spec-driven-dev/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 9 skills cost 1,462 tokens a session between them.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ticket-to-pr 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 today.

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.

plugin/.claude-plugin/plugin.json · 21 lines

What it actually says

{
  "name": "ticket-to-pr",
  "version": "1.11.1",
  "description": "Parallel-batch spec-driven feature workflow (spec-setup, spec-investigate, spec-create, spec-implement, spec-verify, spec-review, spec-checkpoint, spec-ship) plus a portable SEO/GEO operations skill (generative-seo) for any codebase.",
  "author": {
    "name": "Benjamin Thomas",
    "url": "https://github.com/benjaminthomas"
  },
  "keywords": [
    "spec-driven-development",
    "feature-workflow",
    "parallel-agents",
    "seo",
    "geo",
    "productivity"
  ],
  "homepage": "https://github.com/benjaminthomas/spec-driven-dev",
  "repository": "https://github.com/benjaminthomas/spec-driven-dev",
  "icon": ".claude-plugin/icon.png"
}
Contents

What it installs

The manifest is a name and a version. 9 skills travel with it, and installing the plugin installs all of them — 1,462 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.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. today First seen · 21 lines scan A fa33da32bef3

Subscribe to this mod's changes

ticket-to-pr is a plugin published in the GitHub repository benjaminthomas/spec-driven-dev (2 stars, last pushed today), 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-11-11.

Related

ticket-to-pr compared with plugins from other repositories

ticket-to-pr next to 6 plugins from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ticket-to-prbenjaminthomas/spec-driven-devPlugin2todayMITA—Claude Code
humanizerblader/humanizerPlugin68kyesterdayMITA—Claude Code
claude-plugins-official marketplaceanthropics/claude-plugins-officialPlugin47ktodayApache-2.0A—Claude Code
nextjsvercel/next.jsPlugin143ktodayMITA—Claude Code
themes-examplegoogle-gemini/gemini-cliPlugin109ktodayApache-2.0A—Gemini CLI
knowledge-work-plugins marketplaceanthropics/knowledge-work-pluginsPlugin35kyesterdayApache-2.0A—Claude Code
code-modernizationanthropics/claude-plugins-officialPlugin47ktodayApache-2.0A—Claude Code