Update-in-a-Box

A reusable Claude skill that drafts bi-weekly PL Infra Leads updates — OKR progress + 2-week outlook, rendered in chat with R/Y/G status indicators.

Built for any PL Infra team (Polaris, PLCS, Infra Comp, U.S. Entities, etc.). Generalized from the PLAA team's workflow.

---

What it produces

Two sections, rendered directly in your chat thread with R/Y/G (🔴/🟡/🟢) status indicators on each KR:

1. OKR Progress Updates — one block per KR, status emoji + label, 1–3 bullets describing what changed in the last two weeks
2. 2-Week Outlook — forward-looking plans organized into the topic buckets your team defines

You copy-paste the output into your team's Google Doc. If you'd rather have a .docx or have Claude append directly to your running Drive doc, ask for that as a follow-up — those are optional, not default.

---

Repo structure

update-in-a-box/
├── README.md                       # this file
├── LICENSE
├── SKILL.md                        # the skill itself (Claude reads this when triggered)
├── team-config.template.yaml       # one-time setup file per team
├── example-prompts.md              # sample prompts for triggering common workflows
└── releases/
    └── update-in-a-box.skill       # installable bundle (download from Releases)

---

Install

1. Download the latest update-in-a-box.skill from Releases
2. In Cowork, open the skill panel and click Save skill
3. Drop the file in and confirm install

That's it — the bundle expands into the four files above automatically.

---

First-time setup (5–10 min, per team)

1. Copy team-config.template.yaml into your team's project folder (or your Claude Project's knowledge) and rename it team-config.yaml
2. Fill in your team name, KRs, DRIs, and outlook buckets
3. Point Claude at your default sources (Notion DB URL, Slack channel, the Google Doc that hosts your running update, etc.)
4. Add any standing context — code names, sensitive items, things you don't want to re-explain every cycle

If you skip this and just ask Claude to draft, it will ask you the setup questions on the fly and offer to save your answers.

---

Each cycle

Just ask Claude. Some examples:

"Draft this cycle's bi-weekly PL Infra Leads update. Pull from Notion."

"Draft the bi-weekly update from these notes: [paste]"

"Update the 2-week outlook based on the new sprint planning doc I just added."

Claude will:

• Use your saved team config (KRs, buckets, DRIs)
• Pull from whichever sources you've connected, or read pasted/attached content
• Avoid repeating content from your prior bi-weekly update
• Use placeholder language for anything you've flagged as sensitive
• Render the draft directly in chat with R/Y/G indicators on each KR — ready to copy-paste

See example-prompts.md for more triggers.

---

What this does NOT do

• It does not invent metrics — if a number isn't in the source notes you give Claude, Claude will flag the gap rather than guess.
• It does not auto-send. You always review before posting to the team channel or sharing with leads.

---

Contributing

Issues and PRs welcome. Please open an issue first for substantial changes so we can discuss before you invest time.

---

License

MIT — see LICENSE.

---

Maintainer

Originally generalized from the PLAA bi-weekly skill by Theresa Therriault. Adjustments and improvements welcome — open a PR or message her in Slack.