|
| 1 | +# Roundup |
| 2 | + |
| 3 | +Status briefing generator that learns how you communicate. |
| 4 | + |
| 5 | +Roundup watches your work across GitHub, email, Teams, Slack, and other tools, then drafts status updates and briefings in your own voice for any audience you define. |
| 6 | + |
| 7 | +## The Problem |
| 8 | + |
| 9 | +Managers and team leads spend hours each week assembling status updates from scattered sources: scanning PR activity in GitHub, reading email threads for decisions, checking Teams or Slack for context, then rewriting all of it for different audiences at different levels of detail. |
| 10 | + |
| 11 | +The data to write these updates already exists. The work is in gathering it and packaging it. Roundup automates the gathering and drafting. You provide quality control and hit send. |
| 12 | + |
| 13 | +## How It Works |
| 14 | + |
| 15 | +**First time (5 minutes):** Run the setup skill. It asks about your role, your audiences, and where your team's work happens. Then you paste in an example or two of updates you've already written. From those examples, it learns your format, tone, structure, and what you include vs. skip. |
| 16 | + |
| 17 | +**Every time after:** Tell roundup which audience you're writing for. It pulls fresh data from your configured sources, synthesizes across them, and drafts a briefing matching your style. |
| 18 | + |
| 19 | +## Installation |
| 20 | + |
| 21 | +```bash |
| 22 | +copilot plugin install roundup@awesome-copilot |
| 23 | +``` |
| 24 | + |
| 25 | +## Getting Started |
| 26 | + |
| 27 | +### First-Time Setup |
| 28 | + |
| 29 | +``` |
| 30 | +use roundup-setup |
| 31 | +``` |
| 32 | + |
| 33 | +The setup flow walks you through: |
| 34 | +- Describing your role and team |
| 35 | +- Pasting in example updates you've already written |
| 36 | +- Defining your audiences (leadership, team, partners, etc.) and what each one cares about |
| 37 | +- Identifying where your team's work and conversations happen |
| 38 | + |
| 39 | +### Generating a Briefing |
| 40 | + |
| 41 | +``` |
| 42 | +use roundup |
| 43 | +``` |
| 44 | + |
| 45 | +Or be more specific: |
| 46 | + |
| 47 | +``` |
| 48 | +use roundup -- generate a leadership briefing covering this past week |
| 49 | +``` |
| 50 | + |
| 51 | +``` |
| 52 | +use roundup -- draft a team update since Monday |
| 53 | +``` |
| 54 | + |
| 55 | +## What's Included |
| 56 | + |
| 57 | +| Skill | What It Does | |
| 58 | +|-------|-------------| |
| 59 | +| `roundup-setup` | Interactive onboarding that learns your style, audiences, and data sources | |
| 60 | +| `roundup` | Generates draft briefings from your config on demand | |
| 61 | + |
| 62 | +## What It Can Pull From |
| 63 | + |
| 64 | +Roundup adapts to whatever tools are available in your environment: |
| 65 | + |
| 66 | +| Source | What It Looks For | |
| 67 | +|--------|-------------------| |
| 68 | +| GitHub | PRs, issues, commits, review activity across your configured repos | |
| 69 | +| M365 / WorkIQ | Email threads, Teams messages, calendar events, shared docs | |
| 70 | +| Slack | Channel messages, threads, announcements | |
| 71 | +| Google Workspace | Gmail, Calendar, Drive activity | |
| 72 | + |
| 73 | +During setup, roundup discovers which of these you have access to and configures itself accordingly. If you add new tools later, re-run setup to include them. |
| 74 | + |
| 75 | +No API keys or additional setup required beyond what's already configured in your Copilot CLI environment. |
| 76 | + |
| 77 | +## What Makes It Different |
| 78 | + |
| 79 | +**It learns from your examples.** Rather than forcing you into a template, roundup analyzes how you actually write and replicates that style. Your briefings sound like you wrote them. |
| 80 | + |
| 81 | +**It works with whatever you have.** GitHub only? Fine. Full M365 suite? Great. Mix of Slack and Google? Works too. The setup flow discovers your environment and adapts. |
| 82 | + |
| 83 | +**Multiple audiences, one setup.** Define different audience profiles with different detail levels and formats. Same underlying data, different output for each. |
| 84 | + |
| 85 | +**Your config is a readable file.** Everything roundup learned lives in `~/.config/roundup/config.md` -- plain markdown you can open, read, and hand-edit anytime. No opaque settings or hidden state. |
| 86 | + |
| 87 | +## Reconfiguring |
| 88 | + |
| 89 | +To start setup over from scratch: |
| 90 | + |
| 91 | +``` |
| 92 | +use roundup-setup |
| 93 | +``` |
| 94 | + |
| 95 | +It will ask before overwriting your existing config. |
| 96 | + |
| 97 | +To make small adjustments, just open `~/.config/roundup/config.md` in any text editor. The file is written in plain English and organized by section. Your changes are respected on the next run. |
| 98 | + |
| 99 | +## License |
| 100 | + |
| 101 | +MIT |
0 commit comments