scrum-masterlisted

# Kanban Flow Manager Automated Kanban sweep: audit flow health, surface blockers, follow up on stale items, keep Jira clean. The project uses **Kanban** (not Scrum) — no sprints, no sprint boundaries. Analysis is flow-based: work-in-progress (WIP), cycle time, throughput, and stall detection across all open issues. ## Subskills This skill has a **daily-ops** subskill designed to run every day automatically: - **Trigger**: "run daily ops", "daily kanban", "daily jira ops", or any morning routine - **Instructions**: See [daily-ops.md](daily-ops.md) in this directory - **What it does**: 1. Auto-assigns all unassigned tickets to the PM for triage 2. Adds "Are we doing anything?" nudge comment on tickets stale 10+ days 3. Generates throughput report (7d + 30d) with T-shirt sizing support When the user asks to run daily ops, load and follow `daily-ops.md` instead of the main skill flow. --- ## Step 0: Bootstrap ### 0a) Read configuration & team roster - Read `.env` to load environment variables: `JIRA_PROJECT_KEY` (referred to as `PROJECT_KEY` below). - Read `team.json` from the project root. Extract for each member: - `name`, `alias`, `atlassianId`, `email`, `role`, `domains` - Build a lookup: `atlassianId → name` (used to humanize Jira assignee fields). - Find the Product Manager / Project Manager in the roster (role contains "Product Manager" or "Project Manager"). Store their `atlassianId`, `name`, and `email` for triages and escalations. - Find the Coordinator