YOUR-TEAM-config-template.yaml

# PL Infra Leads Bi-Weekly Update — Team Config Template
#
# Fill this out once for your team. Save it as `team-config.yaml` in the same
# folder you keep your bi-weekly updates in (or in your Claude Project's
# knowledge folder). The pl-infra-biweekly-update skill will read it and reuse
# your KRs, DRIs, and outlook buckets every time, so you don't have to re-explain
# the team to Claude.
#
# Anything you don't know yet, leave blank — Claude will ask.

team:
  name: ""                         # e.g. "Polaris", "PLCS", "Infra Comp"
  audience: "PL Infra Leads"       # leave as-is unless your audience differs
  lead_dri: ""                     # the person responsible for sending the update
  cadence: "bi-weekly"             # bi-weekly is standard; some teams do weekly

# ─── KRs to cover in OKR Progress section ────────────────────────────────────
# List every KR your team owns this quarter. Claude will write one section per KR.
# Use the status field to set a default; Claude will update it based on the
# notes you supply each cycle.
key_results:
  - id: "KR1"
    title: ""                      # e.g. "Land 5 net-new infra customers"
    description: ""                # one sentence — what success looks like
    dri: ""                        # name of the directly responsible individual
    status: "🟢 On Track"          # 🟢 On Track / 🟡 Slightly Behind / 🔴 At Risk / ⚪ Not Started

  - id: "KR2"
    title: ""
    description: ""
    dri: ""
    status: "🟢 On Track"

  # Add more KRs as needed — duplicate the block above.

# ─── Outlook buckets for the 2-Week Outlook section ──────────────────────────
# These are the topic groupings Claude will organize forward-looking work into.
# Pick the names your team actually uses. 3–6 is typical. Buckets with no
# active items get omitted automatically.
outlook_buckets:
  - "Adoption"
  - "Product"
  - "Marketing"
  - "Hiring"
  # - "Compliance"
  # - "Partnerships"

# ─── Where Claude should pull source material from ───────────────────────────
# Tell Claude which connectors/sources to default to. Leave blank if you'd
# rather paste notes manually each cycle.
sources:
  notion:
    enabled: false
    meeting_notes_query: ""        # e.g. "<your team> weekly sync"
    sprint_tasks_db_url: ""        # full Notion URL to your sprint tasks DB
    okr_db_url: ""                 # full Notion URL to your OKR DB
  slack:
    enabled: false
    channels: []                   # e.g. ["#polaris-team", "#polaris-standup"]
  google_drive:
    enabled: false
    bi_weekly_doc_url: ""          # the Google Doc that hosts the running update
    folder_url: ""                 # folder where meeting notes live
  metrics:
    dashboard_url: ""              # PostHog / Mixpanel / Looker / etc.
    notes: ""                      # which metrics matter — MAU, conversion, etc.

# ─── Standing context Claude should remember every cycle ─────────────────────
# Code names, ongoing initiatives, sensitive items, jargon. The PLAA team uses
# this for things like "Schrödinger's Token", "PLVH approval status", and
# buyback cadence. Anything Claude should know without you re-explaining it.
standing_context: |
  (Paste any persistent context here. Bullet points or prose both work.)

# ─── Sensitivities & placeholder language ────────────────────────────────────
# Items where Claude should use *[Placeholder: ...]* language instead of
# committing to a phrasing — typically things gated on external announcements,
# legal sign-off, hiring decisions, etc.
sensitivities:
  - ""                             # e.g. "Don't mention the Q3 buyback until participant comms go out"

# ─── Prior update reference ──────────────────────────────────────────────────
# So Claude can avoid repeating content already covered.
prior_update:
  location: ""                     # URL or file path to your last bi-weekly update
  notes: ""                        # anything Claude should specifically NOT repeat