/daily-summary

Turn the state that state-sync keeps mirrored across both trackers into a summary you can paste into a discussion — the daily standup, or a progress review on one task. Because every task carries a current "AI Context" block (GitHub Issue) mirrored to ClickUp, the summary needs no extra digging.

Three modes

Default — daily standup digest (/daily-summary)

Aggregate the current actor's open work and produce a short standup note. Pull from both trackers and correlate by CU-id so one work item is one line, not two:

1. ClickUp — the actor's product tasks + their R&D child tasks (clickup_filter_tasks); read the ai_context mirror field for the gist.
2. GitHub — the actor's open Issues (their "AI Context" block) and open/recently-merged PRs.
3. Correlate ClickUp ↔ GitHub by CU-id; prefer the GitHub Issue "AI Context" as the detailed source, the ClickUp task for product framing/priority.

Output (tight — a few lines per bucket, link each item):

**Daily — <actor>, <date>**
🚢 Shipped:      <merged PRs / closed tasks since yesterday>
👀 In review:    <PRs awaiting review> — who's waiting on whom
🔨 In progress:  <task — current phase + next step, from AI Context>
⛔ Stuck:        <blockers, with the specific ask>
🙋 Need help:    <where input/review is needed>

Single-task — progress summary (/daily-summary <task | cu-id | issue>)

For a progress discussion on one task: resolve the task, then produce a fuller summary from its AI Context block + every linked GitHub Issue + PR:

• What's done — completed plan steps + merged PRs.
• Current phase + next step — from the AI Context block.
• Key decisions — the load-bearing choices recorded along the way.
• Blockers / risks — open items and the ask.
• Links — ClickUp parent + child tasks, GitHub Issues, PRs.

Period — accomplishments digest (/daily-summary --since 30d | --month | --year)

For a 1:1 / monthly / yearly review: "what did I get done this month/year?". Aggregate the actor's completed work over the window — merged PRs, closed Issues, closed ClickUp tasks — into an accomplishments digest grouped by theme.

Code before model: the windowing, grouping, counting, and time-bucketing are done by scripts/period-summary.mjs, not tallied in prose. The model only fetches and narrates. Same inputs → same totals.

1. Fetch the window (resolve the actor first):

   • Merged PRs — search_issues is:pr is:merged author:@me merged:>=<since>.
   • Closed Issues — is:issue is:closed assignee:@me closed:>=<since>.
   • Closed ClickUp tasks — clickup_filter_tasks with a closed/done status and a date in range.
   • For --month/--year derive <since> from the calendar; for --since 30d it's relative.

2. Normalize each to the script's input shape — set date to the merge/close date and theme from the item's domain:* label (GitHub) or ClickUp list/tag (uncategorized if none); repo for GitHub items.

3. Aggregate in the script — write the array to a temp file and run it:

   node scripts/period-summary.mjs --month  --file /tmp/period-items.json
   node scripts/period-summary.mjs --year   --file /tmp/period-items.json
   node scripts/period-summary.mjs --since 30d --file /tmp/period-items.json

   It returns { window, totals, byTheme[], byPeriod[], skipped[] } — --year buckets by month, shorter windows by week.

4. Narrate for the review:

   **<window.label> — <actor>**  (<totals.prs> PRs · <totals.issuesClosed> issues · <totals.tasksClosed> tasks)
   <per theme, highest-count first>
     • <theme> (<count>): <a few headline items, linked>
   Cadence: <byPeriod sparkline — e.g. May 4 · Jun 7>

   If skipped[] is non-empty (items with no close/merge date), say how many were dropped — don't silently undercount.

Boundaries

• Read-only. Produces text; never changes a status, merges, or writes to a tracker. To persist state, that's state-sync; to act on an item, /continue / /pr-review / /done.
• Reports reality. If a task has no AI Context block (state-sync never ran), say so — don't invent progress. If a tracker is unreachable, summarize what was reachable and name what was skipped.
• For "what's on my plate right now, grouped by urgency" rather than a postable summary, use /status.