team-pex

Claude skills for the Personio Payroll Experience (PEX) team.

Installation

claude plugin install team-pex@personio-claude-code-marketplace

What does this plugin do?

PEX-specific workflows that don't fit in personio-common or personio-eng-frontend and aren't owned by a sibling team plugin.

Skill	What it does	Lifecycle
`firefighting-recap`	Summarises a PEX firefighting shift into the PEX firefighter tracker spreadsheet format — pulls the engineer's Slack activity, classifies each item, estimates hours, and writes ready-to-paste Markdown + TSV.	Experimental

`firefighting-recap`

Run after your shift to draft the row(s) you'd otherwise type into the PEX firefighter tracker spreadsheet by hand.

What you need

Slack access via the claude.ai Slack MCP connector (your own user ID is read from the auth context — no setup).
Your firefighter handle (@ff_pay_pex) — recorded in the output header, not required as input.

Quick start

/firefighting-recap
/firefighting-recap 8-12 June
/firefighting-recap last week

The skill:

Resolves the shift window (Mon–Fri before today, or whatever you pass).
Paginates through your Slack messages in the PEX firefighter channels.
Classifies each item into Bug / Investigation / Team Collaboration / Incident (with explicit promotion rules — e.g. an Investigation that ships a fix in the same week becomes a Bug).
Estimates hours per item against a calibration table (one-line ping ≈ 0.5h, deep RC dig ≈ 4h, full-day incident ≈ 6h+).
Saves both formats to ~/Documents/mds/:
- firefighting-cw<NN>.md — table for skim/review/sharing in chat.
- firefighting-cw<NN>.tsv — tab-separated, pastes straight into the tracker spreadsheet (Sheets auto-splits on tabs).
Surfaces the cat … | pbcopy one-liner and any judgment calls worth overriding.

Why would you want this?

End-of-shift admin in under a minute instead of scrolling back through a week of Slack.
Consistent format — same columns, same categories as the team tracker, so manager-readable without re-formatting.
Auditable — every row links back to the source Slack permalink / PR / Jira ticket; no hand-waved hours without a thread to point at.

Customising for other rotations

The skill body hard-codes the PEX firefighter channels (#not_pay_alerts, #not_payroll_bugs, #not-payroll-experience-alerts, #team-payroll-experience, #cir_pay_eng, #cir_productdev_eo). If a sibling team wants to adopt it, fork the skill into their own team-* plugin and swap the channel list — everything else (categorisation rules, hour calibration, output format) generalises.