em-intel_skill

Overview

This skill provides Engineering Manager Intelligence to track team performance, engineer contributions, and project health across GitLab/GitHub and Jira/GitHub Issues. It produces actionable briefs, end-of-day reviews, team reports, epic health checks, and configurable weekly newsletters delivered via Slack, Telegram, email, or print. It maps feature branches to tickets to surface who worked on what and highlights stalled work and quiet engineers.

How this skill works

It ingests repository and ticket system data using adapters for GitLab, GitHub, Jira, and GitHub Issues, then runs core analysis: branch→ticket mapping, merge and PR trends, cycle time, and epic health. Commands generate targeted outputs (morning brief, EOD review, team report, newsletter) and a delivery module routes results to Slack, Telegram, email, or stdout. Configuration is environment-driven so you can switch providers and delivery channels without code changes.

When to use it

• Start-of-day morning brief to see yesterday's merges, open PRs older than 3 days, quiet engineers, and stalled epics.
• End-of-day review summarizing today’s merges, new PRs, contributor list, and cycle time trends.
• Generate a full team-report for performance reviews or sprint retrospectives.
• Investigate contributions by asking who worked on a specific ticket or branch.
• Detect stalled epics and unassigned work during planning or backlog grooming.
• Send a weekly newsletter digest to stakeholders summarizing progress and risks.

Best practices

• Connect the correct code provider and ticket system via environment variables (EM_CODE_PROVIDER, EM_TICKET_PROVIDER).
• Use the branch naming convention that references ticket IDs so branch→ticket mapping is accurate.
• Schedule automated morning-brief and newsletter runs to Slack/Email for consistent stakeholder updates.
• Tune time thresholds for ‘quiet engineers’ and ‘stalled’ items to match your team cadence.
• Combine EOD reviews with team_report exports for longitudinal trend analysis.

Example use cases

• /morning-brief posted to Slack showing yesterday’s merges and PRs older than 3 days.
• /eod-review run at day end to capture today’s merges and contributor activity for managers.
• /team-report --days 30 for a 30-day performance snapshot for an upcoming 1:1.
• Run contributions --engineer Alice to see branches mapped to Jira tickets she touched.
• epic-health to find stalled or unassigned epics before sprint planning.
• newsletter --week to email a weekly digest to execs and product owners.