playbooks

home / skills / athola / claude-night-market / github-initiative-pulse

github-initiative-pulse skill

/plugins/minister/skills/github-initiative-pulse

This skill generates markdown digests and CSV exports from GitHub issues and PRs to support weekly status updates and stakeholder briefings.

npx playbooks add skill athola/claude-night-market --skill github-initiative-pulse

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
2.3 KB
---
name: github-initiative-pulse
description: 'Outputs markdown digests and CSV exports for GitHub issues and PRs.
  Use when creating status reports, weekly updates, stakeholder briefings, generating
  GitHub comment digests, tracking initiative health. Do not use when release gates/readiness
  - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator.'
category: project-management
tags:
- github
- projects
- reporting
- status
- dashboards
dependencies: []
tools:
- minister-tracker
provides:
  reporting:
  - status-digest
  - github-comment
  governance:
  - blocker-radar
  - initiative-health
usage_patterns:
- weekly-status
- issue-digests
- release-briefings
complexity: foundational
estimated_tokens: 650
progressive_loading: true
modules:
- modules/status-digest.md
- modules/github-comment-snippets.md
---

# GitHub Initiative Pulse

## Overview

Turns tracker data and GitHub board metadata into initiative-level summaries. Provides markdown helpers and CSV exports for pasting into issues, PRs, or Discussions.

## Ritual

1. Capture work via `tracker.py add` or sync from GitHub Projects.
2. Review blockers/highlights using the **Blocker Radar** table.
3. Generate GitHub comment via `tracker.py status --github-comment` or module snippets.
4. Cross-link the weekly Status Template and share with stakeholders.

## Key Metrics

| Metric | Description |
|--------|-------------|
| Completion % | Done tasks / total tasks per initiative. |
| Avg Task % | Mean completion percent for all in-flight tasks. |
| Burn Rate | Hours burned per week (auto-calculated). |
| Risk Hotlist | Tasks flagged `priority=High` or due date in past. |

## GitHub Integrations

- Links every task to an issue/PR URL.
- Supports auto-labeling by referencing `phase` in the tracker record.
- Encourages posting digests to coordination issues or PR timelines.

## Exit Criteria

- All initiatives represented with updated metrics.
- Markdown digest pasted into relevant GitHub thread.
- Risk follow-ups filed as issues with owners + due dates.
## Troubleshooting

### Common Issues

If metrics appear outdated, ensure `tracker.py` has successfully synced with GitHub. If the Markdown digest renders incorrectly in GitHub, check for unescaped characters in task titles or missing newlines between table rows.

Overview

This skill turns GitHub issues, PRs, and project board data into compact initiative-level digests and CSV exports. It produces ready-to-post Markdown comment bodies and machine-friendly CSV for status reports, stakeholder updates, or coordination threads. Use it to surface completion, burn, and risk across initiatives quickly.

How this skill works

It inspects tracker records and synced GitHub Projects to compute per-initiative metrics like completion percentage, average task progress, burn rate, and a risk hotlist. It links each entry back to the original issue or PR URL, formats summaries as Markdown tables or CSV rows, and can generate GitHub comment payloads for pasting into issues or PR timelines. Syncing ensures fresh metrics; the tool provides helpers for block lists and cross-linked weekly status templates.

When to use it

  • Preparing weekly status reports or executive digests
  • Posting a concise update to a GitHub issue, PR, or Discussion
  • Tracking initiative health across multiple repos or projects
  • Identifying and surfacing blockers for a standup or review
  • Exporting CSVs for offline analysis or stakeholder slides

Best practices

  • Sync tracker data with GitHub before generating digests to avoid stale metrics
  • Keep task titles clean and escape special characters to ensure Markdown renders correctly
  • Use the Blocker Radar table to highlight immediate follow-ups with owners and due dates
  • Include links to issues/PRs so readers can drill into details from the digest
  • Combine the Markdown digest with a short human summary when sharing with stakeholders

Example use cases

  • Weekly engineering status emailed to stakeholders with inline GitHub digest
  • Sprint review: paste initiative summaries into the retro or planning issue
  • Risk triage: generate a Risk Hotlist to assign owners and deadlines
  • Cross-team coordination: share CSV exports for program managers to import into spreadsheets
  • Automated comment: publish the status snippet to a coordination issue or PR timeline

FAQ

Can this replace release gate checks?

No. Do not use this for release gates or readiness checks; use a dedicated release-health-gates workflow for gate-specific criteria.

Is this suitable for project planning and specs?

No. This skill focuses on tracking and reporting initiative health. For planning and spec orchestration, use the spec-kit orchestrator workflow.

Why do metrics look stale?

Ensure tracker.py has completed a successful GitHub sync. Failed syncs or rate limits can cause outdated metrics; re-run sync and regenerate the digest.

What causes Markdown rendering issues in GitHub?

Unescaped special characters or missing blank lines between table rows. Clean task titles and verify newline formatting before posting.