Prod Dashboard

1c. GitHub

Read the latest GitHub report in workspace/projects/github-reviews/ (most recent file [C] *-github-review.html). Extract:

• Open PRs
• Community issues
• Stars this week
• Latest release

1d. Community

Read the latest community pulse in workspace/community/reports/daily/ or weekly in workspace/community/reports/weekly/. Extract:

• WAM (Weekly Active Members)
• Overall sentiment
• Support tickets
• Docs gaps

1e. Financial

Read the latest strategy digest in workspace/strategy/digests/ (most recent file). Extract:

• MRR
• Subscriptions
• Runway
• Sales pipeline

1f. Calendar

Use /gog-calendar to list today's events.

1g. Meetings

Read workspace/meetings/summaries/ or workspace/meetings/summaries/ — last 5 meetings. Extract:

• Date, title, participants, action items

1h. Routine metrics

Read ADWs/logs/metrics.json for status of each automated routine:

• Name, agent, last run, average duration, success rate

1i. Morning Briefing

Read today's morning briefing at workspace/daily-logs/[C] YYYY-MM-DD-morning.html if it exists, to supplement calendar and priority task data.

Step 2 — Calculate health badges

For each area, define the status (CSS class):

• saudavel (green): all good, metrics within expectations
• misto (yellow): some areas of concern
• risco (red): serious problems requiring action

Criteria:

• Product: blockers > 0 = misto; blockers > 3 = risco; sprint progress < 50% with >60% of time elapsed = risco
• Community: negative sentiment = risco; docs gaps > 5 = misto
• Financial: MRR declining = misto; runway < 6 months = risco
• Routines: any routine with rate < 80% = misto; rate < 50% = risco

Step 3 — Generate dashboard HTML

Read the template at .claude/templates/html/custom/dashboard-consolidation.html and replace ALL {{PLACEHOLDER}} with the collected data.

For dynamic rows (marked with <!-- TEMPLATE -->), generate the correct HTML:

Calendar rows

<div class="metric-row">
  <div class="mr-label">HH:MM</div>
  <div class="mr-value">Event name</div>
</div>

Priority tasks rows

<div class="list-item">Task description</div>

Meetings rows

<tr>
  <td>DD/MM</td>
  <td>Meeting name</td>
  <td>Person 1, Person 2</td>
  <td>N action items</td>
</tr>

Routines rows

<tr>
  <td>Routine Name</td>
  <td>@agent</td>
  <td>DD/MM HH:MM</td>
  <td>XXs</td>
  <td><span class="rotina-rate high/medium/low">XX%</span></td>
  <td><div class="rotina-status"><div class="rotina-dot ok/falha"></div></div></td>
</tr>

Attention points

Consolidate into bullets the items requiring immediate attention. Examples:

• Sprint blockers
• PRs without review for more than 2 days
• Negative community sentiment
• Failing routines
• Declining MRR

If there are no attention points, write "No attention points at the moment."

Step 4 — Save

Save the filled HTML to:

workspace/daily-logs/[C] YYYY-MM-DD-dashboard.html

Step 5 — Confirm

Present a short summary:

## Dashboard generated

**File:** workspace/daily-logs/[C] YYYY-MM-DD-dashboard.html
**Health:** Product {status} | Community {status} | Financial {status} | Routines {status}
**Alerts:** {N} attention points

Notify via Telegram

Upon completion, send a short summary via Telegram to the user:

• Use the Telegram MCP: reply(chat_id="YOUR_CHAT_ID", text="...")
• Format: emoji + routine name + health status of each area (1-3 lines)
• If there were no updates, send anyway with "no updates"