Onboarding our new scrum master: Claude Tag

I manage a globally distributed team and I had no idea what everyone was doing every day. Yasin is in Australia, Niko was in Denmark for a few days, Daryl ships at midnight, I get up at 5 am, and the rest of the team is equally spread. There is no globally convenient time slot available.

No shared time zone means no live check-in, so the only place status can come from is the work itself: commits, tickets, messages.

The real problem is that status truth is split across Github, Slack, and Jira, and reconciling it every day isn’t anyone’s job.

• We still need status updates so everyone knows what everyone else is working on
• Typing status updates is a pain in the ass, no one likes doing it
• Existing tools assume you only work within their platform

Status updates shouldn’t be a report someone writes. It shouldn’t require someone to be online at 2am in their local timezone. We already have all the data needed, it just needs to be reconstructed and someone (me) has to close the loop on the blockers.

Welcome, FNG

Claude Tag is Anthropic’s native Slack integration. It’s a 24/7 AI-driven teammate in Slack. You can tag him with @Claude to assign tasks, ask questions, share context, and collaborate.

We added Claude Tag to our team channel and asked him to check in with each team member at the end of their day. If it’s correct, the team member confirms it and continues on.

Status update complete.

He looks for relevant work like PRs, commits, and tickets closed to pre-populate your status update. This saves the mental context switching from “what did I do today?” to just identifying the items missing from that list. Team members can reply to Claude and their changes get written back live. At the end of the day (Pacific Time), Claude posts a summary of everyone’s activity in one post, for everyone to see.

What he got wrong, and the fix

Yasin called out Claude Tag’s first draft for missing three of his tickets because he only pulled tickets linked to open PRs, not the full Jira queue. We updated his instructions to pull the status from actual system activity: merges, PR states, ticket activity. Now he presents a status update from all our data sources and asks “does this cover it, any blockers?”

What he caught on his own

In one update, Claude Tag noticed Daryl had an overdue ticket that was still In Progress. He offered to either move the due date to Friday or mark it done. Daryl’s reply “Yup, move it to 9/4” triggered him to update the due date in Jira.

In another message, Daryl had been blocked on Cloudflare permissions previously. Claude Tag followed up to make sure the blocker was cleared. When team members are blocked, I get tagged directly to clear the blocker.

He also corrects himself when wrong. In one exchange, he had the date wrong. In the follow-up message he admitted it, made a best-effort guess at the correct answer, and called out what he had done.

Emojis and all: a full-time teammate

We’ve found it extremely useful to have Claude Tag interact with Jira on our behalf. Instead of leaving Slack to create a ticket in Jira, we now just @Claude make a ticket for this. This has saved time and cut down on context-switching. He now triages tickets for us, too. If a ticket has been sitting in our queue, unclaimed for > 48 hours, he picks it up and attempts to resolve the issue.

Claude Tag is now a full-time member of the team. His emoji game is strong, too. That is a requirement if you’re going to succeed on my team. He routinely responds with 👀 or 👍 to acknowledge messages, but grabs relevant emoji when appropriate, such as the beach with umbrella emoji when told to “hit the beach”. During his performance review at the end of the year, I’m going to challenge him to step up with memes and gifs.

What this changes

We didn’t have a Scrum Master on the team, and we were suffering as a result. Using Claude Tag, status updates became a byproduct of the work instead of a tax on it, and silence became visible instead of invisible.