Skip to content

setup-guide.md

Latest commit

 

History

History
77 lines (59 loc) · 3.72 KB

setup-guide.md

File metadata and controls

77 lines (59 loc) · 3.72 KB

Update-in-a-Box — Setup Guide

This guide is set up to enable PL Infra teams (Polaris, PLCS, etc.) to create a PL Infra upate skill for their own team.

Generic setup for PL Infra teams

For Polaris, PLCS, PL Capital, or any other PL Infra team. Roughly 15 minutes of one-time setup, then ~15 minutes per cycle instead of 1+ hour.

Files you'll need

File Purpose
update-in-a-box.skill The installable generic skill bundle
update-in-a-box/team-config.template.yaml Blank config template to fill in for your team
update-in-a-box/README.md Reference doc
update-in-a-box/example-prompts.md Sample prompts that trigger common workflows

Step 1 — Install the skill in Cowork

  1. Open Cowork → Skills panel
  2. Drag update-in-a-box.skill in, or click Save skill
  3. Confirm update-in-a-box appears in your installed skills

Step 2 — Create a Claude Project for your team

  1. New Project → name it after your team (e.g. "Polaris PM", "PLCS Updates")
  2. This keeps your team's context, prior chats, and config in one place — the project's chat history becomes Claude's memory across cycles

Step 3 — Fill out your team-config.yaml

  1. Save team-config.template.yaml to your project folder
  2. Rename it to team-config.yaml
  3. Fill in:
    • Team name + audience (likely "PL Infra Leads")
    • Active KRs — id, title, DRI, status for each KR your team owns this quarter
    • Outlook buckets — the 3–6 topic groupings your team uses for forward-looking work
    • Source connections — Notion DB URLs (sprint tasks, OKRs), Slack channels, the Google Doc that hosts your running bi-weekly update
    • Standing context — ongoing initiatives, code names, anything you don't want to re-explain every cycle
    • Sensitivities — items that need placeholder language (delayed announcements, pending approvals, hires in flight)
    • Prior update location — where your last bi-weekly lives so Claude can avoid repeating it
  4. Add the populated team-config.yaml to your project's Knowledge panel

Step 4 — Connect your tools

Connector Status Why
Notion Required Most teams keep meeting notes + sprint tasks + OKRs in Notion
Slack Optional For pulling channel context
Google Drive Optional For appending directly to the running bi-weekly Google Doc
Gmail Optional If your team's update threads live in email

Skip any you don't use. If you have a different tool stack (Linear, Jira, Confluence), tell Claude in chat — the skill is connector-agnostic.

Step 5 — First test run

In your project, type:

"Draft our bi-weekly PL Infra Leads update."

If your team-config.yaml is fully populated, Claude will pull from your configured sources and draft. If anything's missing, it will ask the setup questions on the fly and offer to save your answers.

Step 6 — Maintenance

  • Each cycle: just prompt Claude. The more it runs in your project, the better it gets at your team's voice.
  • Each quarter: update your team-config.yaml with the new KR list and refreshed standing context.

Triggers that will activate the skill

Any of these prompts will fire Update-in-a-Box:

  • "Draft this cycle's PL Infra Leads update"
  • "Prepare the OKR progress update"
  • "Write the two-week outlook"
  • "Run Update-in-a-Box"
  • "Update the KR status notes"

See example-prompts.md for more variations.

Quick reference — which file goes where

Audience Bundle to install Config to fill out Project knowledge
PL Infra team update-in-a-box.skill Fill out update-in-a-box/team-config.template.yaml and rename to team-config.yaml New project named after their team