Agent Plugins Marketplace
← All plugins

ticket-workflow

v0.11.0

End-to-end issue workflow (make/start/finish/spawn/epic) with a pluggable tracker (GitHub Issues or Jira) and profile

Claude Code1 Skill

By Mario Guerrieri0 GitHub starsUpdated 2 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
1 skill or MCP entry
Source updated
Aug 30, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install ticket-workflow for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install ticket-workflow@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/maguerrieri/claude-toolbox

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/ticket-workflow/.

Plugin files

plugins/ticket-workflow/
├── .claude-plugin/plugin.json
└── skills/ticket-workflow/SKILL.md

Included Skills1

ticket-workflowskills/ticket-workflow/SKILL.md

Use when the user wants to start, pick up, knock out, or begin work on an issue/ticket; to finish, land, merge, or close out a reviewed PR/ticket; to file or create a new issue/ticket from the current discussion, including compound create-and-run requests ("make a ticket for this and spawn it"); to work tickets in parallel or in the background; or to run an epic and its child issues — in any phrasing ("pick up #42", "land PR 7", "file an issue for that bug", "get issues 3 and 5 moving while I'm out", "handle the auth epic"). ALSO use whenever /make-ticket, /start-ticket, /finish-ticket, /spawn-tickets, /start-epic, or /spawn-epic appears anywhere in a message, even mid-sentence ("file an issue and /spawn-tickets it"), and even if this skill is already in context. Tracker-agnostic (GitHub Issues or Jira) with pluggable org profiles; assumes GitHub-hosted code (PRs/CI/merges via gh).

Plugin manifests1

plugins/ticket-workflow/.claude-plugin/plugin.json
{
  "name": "ticket-workflow",
  "description": "End-to-end issue workflow (make/start/finish/spawn/epic) with a pluggable tracker (GitHub Issues or Jira) and profile",
  "version": "0.11.0",
  "author": {
    "name": "Mario Guerrieri"
  },
  "dependencies": [
    "spawn"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[ticket-workflow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/ticket-workflow)