github-initiative-pulse
Generate program dashboards, GitHub-ready comment digests, and CSV summariessourced from Minister's tracker data.Triggers: initiative pulse, status report, weekly update, stakeholder briefing,github dashboard, blocker radar, initiative health, program metricsUse when: creating status reports, weekly updates, stakeholder briefings,generating GitHub comment digests, tracking initiative healthDO NOT use when: release gates/readiness - use release-health-gates.DO NOT use when: project planning - use spec-kit:speckit-orchestrator.Outputs markdown digests and CSV exports for GitHub issues and PRs.
When & Why to Use This Skill
GitHub Initiative Pulse is a specialized Claude skill designed to automate project tracking and stakeholder communication. It transforms raw tracker data and GitHub metadata into high-level program dashboards, markdown-formatted status digests, and CSV summaries. By providing real-time visibility into initiative health, burn rates, and risk factors, it streamlines the reporting process for engineering leads and project managers, ensuring seamless alignment between technical tasks and business objectives.
Use Cases
- Weekly Status Reporting: Automatically generate comprehensive weekly updates and stakeholder briefings that summarize initiative progress and key metrics.
- GitHub Team Coordination: Produce GitHub-ready markdown digests to be pasted directly into Issues, PRs, or Discussions to keep distributed teams synchronized.
- Risk & Blocker Identification: Utilize the 'Blocker Radar' and 'Risk Hotlist' features to proactively identify high-priority bottlenecks and overdue tasks.
- Program Health Monitoring: Track essential KPIs such as completion percentages and burn rates across multiple initiatives to ensure project delivery remains on schedule.
- Data Portability: Export initiative-level data into CSV format for custom analysis, spreadsheet reporting, or long-term record-keeping.
| name | github-initiative-pulse |
|---|---|
| description | | |
| Triggers | initiative pulse, status report, weekly update, stakeholder briefing, |
| Use when | creating status reports, weekly updates, stakeholder briefings, |
| DO NOT use when | project planning - use spec-kit:speckit-orchestrator. |
| version | 1.0.0 |
| category | project-management |
| tags | [github, projects, reporting, status, dashboards] |
| dependencies | [] |
| tools | [minister-tracker] |
| reporting | [status-digest, github-comment] |
| governance | [blocker-radar, initiative-health] |
| complexity | foundational |
| estimated_tokens | 650 |
| progressive_loading | true |
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
- Capture work via
tracker.py addor sync from GitHub Projects. - Review blockers/highlights using the Blocker Radar table.
- Generate GitHub comment via
tracker.py status --github-commentor module snippets. - 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
phasein 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.