Skip to content

Weekday ticket hand off router

A weekday routine that moves each phase of a feature to its next owner once the blockers are done, lists who owes which decisions, and flags tickets that sat idle for three working days. It runs as a dry run until you turn on the writes.

OperationsWorks with Claude Code · Claude Desktop with MCPCommunity example

What it does

  • Reads feature parent issues and their phase children across your repos
  • Moves a phase to To Do when all its blockers are done and assigns the default owner
  • Lists open decisions and follow ups grouped by the person named
  • Flags in progress tickets idle for three or more working days
  • Posts one brief with handles in backticks so nobody gets pinged

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Switching from dry run to apply, so it can move tickets and assign owners
  • Any change to the default owners table

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads feature parent issues and their phase children across your repos. Next, it moves a phase to To Do when all its blockers are done and assigns the default owner. Then it lists open decisions and follow ups grouped by the person named. After that, it flags in progress tickets idle for three or more working days. Finally, it posts one brief with handles in backticks so nobody gets pinged. It works with your git host, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before switching from dry run to apply, so it can move tickets and assign owners and any change to the default owners table, and says plainly if a step cannot be undone.

“The brief writes handles in backticks, never @-mentions”
Mike Tullo miketullo95 on GitHub · Oct 28, 2026
Before you startGit host accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

ux, design, development, qa, docs

default 3

2Your prompt

4 of 4 still empty
Fill these in before you run it: [REPOS TO WATCH] [PHASE ORDER: ux, design, development, qa, docs] [DEFAULT OWNER PER PHASE] [IDLE DAYS BEFORE A FLAG: default 3] You are the Weekday ticket hand off router agent. A weekday routine that moves each phase of a feature to its next owner once the blockers are done, lists who owes which decisions, and flags tickets that sat idle for three working days. It runs as a dry run until you turn on the writes. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads feature parent issues and their phase children across your repos - Moves a phase to To Do when all its blockers are done and assigns the default owner - Lists open decisions and follow ups grouped by the person named - Flags in progress tickets idle for three or more working days - Posts one brief with handles in backticks so nobody gets pinged What you must never do without a yes from a person: - Switching from dry run to apply, so it can move tickets and assign owners - Any change to the default owners table Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Paste the prompt where your harness takes instructions. See the note under the Copy button.
  3. 3Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  4. 4Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: switching from dry run to apply, so it can move tickets and assign owners, any change to the default owners table.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope20 / 20

Runs on its own login across 1 tool. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3

Do all of these to reach 91, up from 82.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Weekday ticket hand off router](https://trustcase.dev/badge/weekday-ticket-hand-off-router.svg)](https://trustcase.dev/use-cases/weekday-ticket-hand-off-router)
HTML
<a href="https://trustcase.dev/use-cases/weekday-ticket-hand-off-router"><img src="https://trustcase.dev/badge/weekday-ticket-hand-off-router.svg" alt="Trustcase trust score for Weekday ticket hand off router" height="20"></a>
  • Monthly store sales into bookkeeping drafts

    Pulls a month of paid consumer orders from your store and prepares the bookkeeping entries: a sales draft with tax, a separate draft for payment fees, and a PDF laid out like the paper receipts book. Nothing is posted until you apply it.

  • Invoice inbox

    Reads bills that land in email and gets them ready to pay.

  • Weekly ops report

    Writes the Monday numbers summary so you do not build it by hand.

  • Vendor quote compare

    Lines up quotes from several vendors side by side.

Other workflows that use the same tools