Github Initiative Pulse

# GitHub Comment Snippets

Use these markdown snippets with `tracker.py status --github-comment` output for richer posts.

## Initiative Scorecard

```
| Initiative | Done | Blockers | Next |
|------------|---------|-------------|--------|
| <Name> | <count> | <issue links> | <key tasks> |
```

## Blocker Radar

```
<details>
<summary>High Risk Issues</summary>

- [ ] [issue-123](link) – Owner: @handle – Mitigation ETA 1/12
- [ ] [issue-456](link) – Owner: @handle – Needs design sign-off

</details>
```

## PR Watchlist

```
### PRs awaiting review
- #1234 Ready for Docs
- #5678 Needs Performance Sign-off
```

## Discussion Template

```
> Posted via Minister Initiative Pulse
> Data refreshed: <timestamp>
```


# Status Digest Blueprint

## Inputs

- `ProjectTracker.get_status_report()` JSON payload.
- Optional GitHub Projects filter (lane, owner).
- Risk label queries (e.g., `label:risk-red state:open`).

## Steps

1. Pull tracker JSON.
2. Identify initiatives with completion < 80%.
3. For each initiative create:
   - 2 key wins (link to merged PRs).
   - 2 active risks (link to issues).
   - Updated ETA derived from due dates.
4. Drop summary into template:

```
### <Initiative>
- Wins: <PR 1>, <PR 2>
- Risks: <Issue 1>, <Issue 2>
- Next Milestone: <Date>
```

5. Include table of metrics using tracker values.

## Tips

- Use GitHub search queries so stakeholders can self-serve deeper context.
- Keep bullet count consistent each week for comparability.
- Add emoji tags to draw attention inside GitHub comments.


---
name: github-initiative-pulse
description: Generates markdown digests and CSV exports for GitHub initiative health. Use when reporting on issue/PR progress across a milestone or project.
alwaysApply: false
category: project-management
tags:
- github
- projects
- reporting
- status
- dashboards
dependencies: []
tools: []
provides:
  reporting:
  - status-digest
  - github-comment
  governance:
  - blocker-radar
  - initiative-health
usage_patterns:
- weekly-status
- issue-digests
- release-briefings
complexity: foundational
model_hint: standard
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 and 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.