tpm-copilot_skill

Overview

This skill is an AI-powered operating system for Technical Program Managers and Project Managers that consolidates Jira, Linear, GitHub, and calendar data to automate program workflows. It generates audience-specific status reports, tracks risks and blockers, prepares meeting agendas, maps dependencies, and produces stakeholder dashboards. The tool adapts to available integrations and saves outputs to program workspaces or delivers them via Slack, email, or Confluence.

How this skill works

The skill connects to configured trackers (Jira or Linear), GitHub, and calendars to pull sprint metrics, tickets, PRs, CI status, meetings, and milestones. It synthesizes those signals into status reports, a risk register, dependency maps, meeting agendas, and action-item lists. Automated scripts run core workflows—status-report generation, risk scanning, meeting prep, and dependency checks—and can deliver results to Slack, email, files, or Confluence. Program-specific config files control thresholds, workstreams, repos, and delivery targets.

When to use it

• Generate weekly executive, engineering, or full program status reports automatically.
• Scan for risks: stale tickets, blocked work, PR bottlenecks, CI failures, or missed commitments.
• Prepare meeting agendas and extract action items from notes for standups, reviews, or exec syncs.
• Map and monitor cross-team dependencies and alert on slips or critical path changes.
• Create stakeholder dashboards and monitor sprint health, velocity, and overdue actions.

Best practices

• Keep per-program config.json up to date with boards, repos, and stakeholder destinations.
• Configure tracker selection (jira or linear) and set sensible thresholds for stale tickets and PR review time.
• Run daily risk scans and schedule weekly status-report delivery via cron for consistent cadence.
• Use templates to standardize exec vs engineering report formats and reduce manual edits.
• Enable webhook or email delivery for key stakeholders to ensure timely visibility.

Example use cases

• Auto-generate a 150–200 word executive summary with RAG status and top 3 risks for Monday leadership updates.
• Detect PRs open >48 hours and create a review bottleneck alert for the engineering manager.
• Prepare a sprint-review agenda with sprint metrics, completed work, and carry-over items before the demo.
• Scan project boards nightly to append new high-severity risks to the program risk register and notify owners.
• Produce a markdown dependency table highlighting upstream slips and export it to Confluence for stakeholders.