🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί TPM Copilot
πŸ¦€ ClawHub

TPM Copilot

by @reighlan

AI-powered operating system for Technical Program Managers and Project Managers. Pulls data from Jira, Linear, GitHub, and calendars to auto-generate status...

Versionv1.0.0
Downloads1,010
#legal#communication#productivity
TERMINAL
clawhub install tpm-copilot

πŸ“– About This Skill

name: tpm-copilot description: "AI-powered operating system for Technical Program Managers and Project Managers. Pulls data from Jira, Linear, GitHub, and calendars to auto-generate status reports, track risks and blockers, manage meeting workflows, map dependencies, and deliver stakeholder dashboards. Use when: (1) generating status reports or program updates, (2) tracking risks, blockers, or stale tickets, (3) preparing meeting agendas or extracting action items, (4) mapping cross-team dependencies, (5) creating stakeholder dashboards, (6) monitoring sprint health or velocity, (7) writing executive summaries, or (8) automating any TPM/PM workflow."

TPM Copilot

Your AI program management operator. Pulls from Jira, Linear, GitHub, and calendars β€” synthesizes everything into status reports, risk alerts, meeting prep, and stakeholder dashboards.

Setup

Dependencies

pip3 install requests

For GitHub: install gh CLI and authenticate (gh auth login).

API Connections (configure in config.json)

  • Jira β€” JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN (Atlassian API token)
  • Linear β€” LINEAR_API_KEY
  • GitHub β€” uses gh CLI (already authenticated) or GITHUB_TOKEN
  • Slack β€” SLACK_WEBHOOK_URL (for report delivery)
  • Calendar β€” iCal URL or Google Calendar API

    • Not all required β€” skill adapts to what's configured.

    Workspace

    tpm/
β”œβ”€β”€ config.json           # API keys, project settings, team config
β”œβ”€β”€ programs/             # Per-program data
β”‚   └── program-name/
β”‚       β”œβ”€β”€ config.json   # Program-specific settings (board IDs, repos, teams)
β”‚       β”œβ”€β”€ reports/      # Generated status reports
β”‚       β”œβ”€β”€ risks/        # Risk register snapshots
β”‚       └── dependencies/ # Dependency maps
β”œβ”€β”€ templates/            # Report templates
β”œβ”€β”€ meetings/             # Meeting notes and action items
└── state.json            # Persistent state (last check timestamps, etc.)

    Run scripts/init-workspace.sh to create this structure.

    Core Workflows

    1. Status Report Generator

    The flagship workflow. Pulls from all connected tools, generates audience-specific reports.

    scripts/status-report.sh --program "my-program" --audience exec
scripts/status-report.sh --program "my-program" --audience eng
scripts/status-report.sh --program "my-program" --audience full
scripts/status-report.sh --program "my-program" --audience exec --deliver slack

    Data pulled:

  • Jira/Linear: sprint progress, tickets by status, velocity, blockers, recent completions
  • GitHub: PRs merged/open/stale, CI status, release tags
  • Calendar: upcoming milestones, meetings this week

    • Audience formats:

  • exec β€” 3-5 bullet executive summary, RAG status per workstream, top risks, key decisions needed. Under 200 words.
  • eng β€” sprint metrics, PR review queue, blockers, velocity trends, upcoming deadlines
  • full β€” comprehensive program update with all sections, dependencies, action items

    • Delivery options:

  • stdout (default) β€” prints to terminal
  • slack β€” posts to configured webhook
  • email β€” sends via Resend/SMTP
  • confluence β€” creates/updates a Confluence page
  • file β€” saves to programs//reports/

    • 2. Risk & Blocker Radar

    Proactive scanning for problems before they become crises.

    scripts/risk-radar.sh --program "my-program"
scripts/risk-radar.sh --program "my-program" --alert     # Send alerts for new risks
scripts/risk-radar.sh --program "my-program" --history    # Show risk trends

    Auto-detected risks:

  • Stale tickets β€” no updates in N days (configurable, default 5)
  • Blocked tickets β€” status = blocked, or flagged
  • PR review bottlenecks β€” PRs open >48h without review
  • Sprint scope creep β€” tickets added mid-sprint
  • Missed commitments β€” tickets rolled over from previous sprint
  • CI failures β€” broken builds on main branch
  • Dependency delays β€” upstream team's deliverables slipping

    • Risk register maintained as JSON in programs//risks/: 

    {
  "id": "RISK-001",
  "severity": "high",
  "category": "delivery",
  "title": "Auth service migration blocked on Team B API",
  "detected_at": "2026-02-24",
  "source": "jira_blocked_ticket",
  "ticket": "PROJ-1234",
  "status": "open",
  "mitigation": "",
  "owner": ""
}

    3. Meeting Autopilot

    Automate meeting prep, notes processing, and follow-up tracking.

    scripts/meeting-prep.sh --program "my-program" --type standup
scripts/meeting-prep.sh --program "my-program" --type sprint-review
scripts/meeting-prep.sh --program "my-program" --type exec-sync
scripts/meeting-prep.sh --program "my-program" --type program-review
    scripts/process-notes.sh --file meeting-notes.md         # Extract action items
scripts/action-tracker.sh --program "my-program"          # Show overdue actions
scripts/action-tracker.sh --program "my-program" --create-tickets  # Create Jira tickets for actions

    Meeting types and auto-generated agendas:

  • standup β€” yesterday's completions, today's focus, blockers (from Jira)
  • sprint-review β€” sprint metrics, completed work, demos, carry-over items
  • exec-sync β€” program RAG, top risks, decisions needed, timeline status
  • program-review β€” full workstream status, dependencies, resource needs

    • Notes processing:

  • Parse markdown notes for action items (lines starting with AI:, TODO:, ACTION:, or [ ])
  • Extract owners and due dates
  • Optionally create Jira/Linear tickets
  • Track completion status across meetings

    • 4. Dependency Tracker

    Map and monitor cross-team dependencies.

    scripts/dependency-map.sh --program "my-program"           # Generate dependency map
scripts/dependency-map.sh --program "my-program" --check   # Check for slips
scripts/dependency-map.sh --program "my-program" --alert   # Alert on at-risk dependencies

    Sources:

  • Jira issue links (blocks/is-blocked-by)
  • Jira/Linear labels (e.g., depends-on:team-b)
  • Manual entries in programs//dependencies/deps.json

    • Output:

  • Markdown dependency table with status
  • Critical path highlighting
  • Alert when upstream dependencies slip

    • 5. Program Dashboard

    Quick terminal dashboard for program health.

    scripts/dashboard.sh --program "my-program"

    Shows:

  • Overall RAG status
  • Sprint progress (% complete, days remaining)
  • Open risks by severity
  • PR review queue
  • Upcoming milestones
  • Action items overdue

    • Configuration

    Program Config (programs//config.json)

    {
  "name": "Project Phoenix",
  "workstreams": [
    {
      "name": "Backend",
      "jira_project": "PHX",
      "jira_board_id": "123",
      "github_repos": ["org/backend-api"],
      "team_lead": "Alice"
    },
    {
      "name": "Frontend",
      "jira_project": "PHX",
      "jira_board_id": "124",
      "github_repos": ["org/web-app"],
      "team_lead": "Bob"
    }
  ],
  "milestones": [
    {"name": "Alpha Release", "date": "2026-03-15", "status": "on-track"},
    {"name": "Beta Release", "date": "2026-04-30", "status": "on-track"}
  ],
  "stakeholders": {
    "exec": ["vp-eng@company.com"],
    "eng": ["#eng-phoenix-slack-channel"],
    "full": ["phoenix-team@company.com"]
  },
  "settings": {
    "stale_ticket_days": 5,
    "pr_review_threshold_hours": 48,
    "sprint_length_weeks": 2,
    "tracker": "jira"
  }
}

    Tracker Selection

    Set settings.tracker to "jira" or "linear". Scripts auto-adapt API calls accordingly.

    Cron Integration

  • Daily standup prep β€” generate at 8:30 AM before standup
  • Daily risk scan β€” run at end of day, alert on new risks
  • Weekly status report β€” generate and deliver Monday AM
  • Action item follow-up β€” check overdue items daily
  • Sprint boundary β€” auto-generate sprint review data on last day of sprint

    • References

  • references/jira-setup.md β€” Jira API authentication and project configuration
  • references/linear-setup.md β€” Linear API setup and GraphQL queries
  • references/report-templates.md β€” Customizing report formats and sections
  • references/risk-categories.md β€” Risk taxonomy and severity definitions

    • βš™οΈ Configuration

    Program Config (programs//config.json)

    {
  "name": "Project Phoenix",
  "workstreams": [
    {
      "name": "Backend",
      "jira_project": "PHX",
      "jira_board_id": "123",
      "github_repos": ["org/backend-api"],
      "team_lead": "Alice"
    },
    {
      "name": "Frontend",
      "jira_project": "PHX",
      "jira_board_id": "124",
      "github_repos": ["org/web-app"],
      "team_lead": "Bob"
    }
  ],
  "milestones": [
    {"name": "Alpha Release", "date": "2026-03-15", "status": "on-track"},
    {"name": "Beta Release", "date": "2026-04-30", "status": "on-track"}
  ],
  "stakeholders": {
    "exec": ["vp-eng@company.com"],
    "eng": ["#eng-phoenix-slack-channel"],
    "full": ["phoenix-team@company.com"]
  },
  "settings": {
    "stale_ticket_days": 5,
    "pr_review_threshold_hours": 48,
    "sprint_length_weeks": 2,
    "tracker": "jira"
  }
}

    Tracker Selection

    Set settings.tracker to "jira" or "linear". Scripts auto-adapt API calls accordingly.