Results for “pass-the-ticket”

ticket-writer

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Breaks a plan, spec, or conversation into tracer-bullet tickets that declare their blocking edges, published to the configured tracker. Use when the user says "break this into tickets" or wants a plan decomposed into vertical slices.

Refine a ticket interactively until it is ready for planning.

Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Classify customer support tickets, emails, or chats by category and priority, draft responses, and document next steps.

Package a customer escalation for engineering, product, or leadership as a decision-ready handoff — impact, timeline, facts vs. hypotheses, and a specific ask with an owner.

Enumerate Active Directory service accounts, request Kerberos TGS tickets, and crack them offline to assess password strength and privilege escalation paths.

Generate an event ticket image with QR code, event name, date, venue, and seat information.

Implement a piece of work based on a spec or set of tickets.

Detect Golden Ticket attacks in Active Directory by analyzing Kerberos TGT anomalies including mismatched encryption types, impossible ticket lifetimes, non-existent accounts, and forged PAC signatures in domain controller event logs.

Creates structured Jira tickets from incident root cause analysis findings, including severity classification and remediation steps.

Guide a visible, verified code walkthrough in Neovim with Terminal Control and Navi, optionally recording the presentation with OBS or retaining terminal evidence.

Manage Zendesk support tickets via the `zd` CLI. Use when the user asks about Zendesk tickets, support tickets, customer issues, helpdesk operations, or ticket triage. Covers listing, searching, creating, updating, and deleting tickets, plus authentication setup and Zendesk search queries. Triggers on tasks involving "zendesk", "zd", "support ticket", "ticket queue", "helpdesk", or "customer support".

Itere em uma PR até que o CI passe. Use quando precisar corrigir falhas de CI, endereçar feedback de revisão, ou continuamente enviar correções até que todas as verificações fiquem verdes. Automatiza o ciclo de feedback-correção-push-aguardar.

Interact with Atlassian Jira from the terminal: search issues, view details, create issues, add comments, list projects, and transition status. Use when the user mentions Jira, a ticket key (e.g. PROJ-123), or asks about issues, bugs, tasks, projects, or sprint work.

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Build throwaway code that answers exactly one design question — a tiny terminal app to feel out logic/state models, or several radically different UI variants switchable on one route. Use when the user wants to "prototype", "mock up", "sketch", "try a few versions", "see what it'd look like", "feel out this state machine", or is stuck choosing between designs they can only judge by seeing or driving them. Also used by the whiteboard skill for napkin-type tickets.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Implement a piece of work based on a spec or set of tickets.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

Put the user in the hot seat — one question at a time until their plan, decision, or idea actually holds up. Use whenever the user says "hot seat me", "grill me", "stress-test this", "poke holes in this", "am I missing anything", or drops a plan and wants it challenged before anyone acts on it — even if they never say the words. Also used as a sub-procedure by the whiteboard and connotation-cop skills.

Verify a Jira issue against the current repository state, then post a Jira comment with a PASS, PARTIAL, FAIL, or BLOCKED verdict. Works in two modes: (a) feature-branch mode, comparing a checked-out branch to its base ref; or (b) main/trunk mode, verifying that an issue is already implemented on the current default branch (typical for stories that have already merged). Use when a user asks whether a branch or merged change completes a Jira ticket, or needs a Jira-visible verification comment.