org-os-updateslisted

# Team OS Updates ## Usage **When to use:** Weekly, to keep the team aware of what's changed in the repo. Run on Monday morning or Friday afternoon. Post output to your team's `#org-os` Slack channel (or equivalent). **Inputs:** Nothing — reads git history and the repo directly. **Output:** A short, scannable update: what's new, what changed, what was removed. A repo that changes silently is a repo people stop trusting. This skill makes changes loud. --- ## THINK: What to surface Pull changes from the last 7 days (or since last update). Look for: 1. **New skills** — added to `skills/` since last update 2. **Modified skills** — existing skills with meaningful changes (not just typos) 3. **New or modified workflows** — additions or changes to `workflows/` 4. **Knowledge updates** — new files in `knowledge/customers/`, `knowledge/market/`, or `knowledge/metrics/` 5. **Ownership changes** — any `owner:` field updates in skill frontmatter 6. **Removals or deprecations** — skills or files removed Use git log to identify changes: ``` git log --since="7 days ago" --name-only --pretty=format:"" ``` Filter to meaningful changes — skip formatting fixes, punctuation corrections, and CLAUDE.md-only updates that don't affect how skills work. --- ## EXECUTE: Output format Keep it short. This is a team communication, not a changelog. PMs should be able to read it in 60 seconds. ``` ## [YOUR COMPANY] Team OS — week of {date} ### New this week - **{skill-name}** — {one line: what