What is ticket-workflow?

A set of instructions for taking a Jira ticket from investigation through implementation, review, and pull-request preparation, while tracking work across agents.

Use it with an MTV ticket or Jira URL to fetch requirements, investigate the codebase, implement the agreed solution, run specialist reviews, and prepare the change for a pull request.

It provides a consistent path from a ticket to reviewed code and requires confirmation before implementation.

ticket-workflow — Cursor rule for Cursor by kubev2v

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/kubev2v/forklift-console-plugin

Made for: Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ticket-workflow/github.svg)](https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ticket-workflow)

Your own site

<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ticket-workflow"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ticket-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ticket-workflow"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ticket-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 922 The whole file, excluding the scripts and references it only reads on demand.

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.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.00922
Opus 5.5	$0.00003	$0.00369
Sonnet 5.5	$0.00001	$0.00184
Haiku 4.5	$0.00001	$0.00092

Measured 1mo ago against content hash 78fd3de389c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ticket-workflow 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 1mo 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.

.cursor/rules/workflows/ticket-workflow.mdc · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ticket Workflow with Agent Tracking

Invoke with: "start working on MTV-XXX", Jira ticket URL, "ticket workflow"

This workflow defines how to execute a complete Jira ticket from analysis to PR using agent tracking.

1. Workflow Steps

When a ticket URL or MTV-XXXX reference is received:

Fetch and analyze the ticket - Understand requirements
Present analysis and solution options - Wait for user to confirm approach
Implement after user confirms - Follow the selected approach
Run review agents - UX, QE, Security, Forklift Expert
Ask to implement recommendations - After each review phase

2. Phase 1: Understand the Issue

Use get_jira tool to fetch the ticket details by key (e.g., MTV-1885)
Use get_issue_comments to read any additional context from the team
Identify key information:
- For bugs: affected version, steps to reproduce, expected vs actual behavior, logs/screenshots
- For features: user story, acceptance criteria, technical requirements, mockups

3. Phase 2: Investigate the Codebase

Based on the ticket description, identify likely affected areas:
- Component mentioned in the ticket
- Error messages that can be searched
- UI elements or API endpoints involved
Search the codebase for related code
Trace the code flow that would be executed
Identify the root cause (bugs) or implementation approach (features)

4. Phase 3: Present Analysis

Present findings to the user:

Root Cause / Approach: Clear explanation
Affected Files: List of files that need modification
Solution Options: Provide 2-3 possible approaches with tradeoffs:
- Option A: [Quick fix] - Description and implications
- Option B: [Proper fix] - Description and implications
- Option C: [Comprehensive fix] - If applicable

5. Phase 4: Implementation (after user selects approach)

Implement the selected fix/feature
Follow project coding conventions (AGENTS.md)
Add appropriate error handling
Consider edge cases

Read the full file on GitHub · 136 lines

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.

1mo ago First seen · 136 lines · 7 tokens per session scan A 78fd3de389c2

Subscribe to this mod's changes

ticket-workflow is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 922 once invoked, about $0.0000 per session on Opus 5.5. 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-30.

Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

ticket-workflow