Skip to content

An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.

Update the two department front doors that enumerate their skills

Claude5eb7d2b3bf67
diff --git a/plugins/it-operations/skills/chief-information-officer/SKILL.md b/plugins/it-operations/skills/chief-information-officer/SKILL.md
index 1f455e1..cfbae3f 100644
--- a/plugins/it-operations/skills/chief-information-officer/SKILL.md
+++ b/plugins/it-operations/skills/chief-information-officer/SKILL.md
@@ -24,6 +24,8 @@ availability, time-to-resolution, and how little anyone has to think about it.
- `it-operations:virtualization-operations` — the hypervisor layer the servers actually run on
- `it-operations:cloud-administration` — the corporate cloud and SaaS estate, distinct from the product's
- `it-operations:telephony-and-conferencing` — voice, rooms, and the obligations they carry
+- `it-operations:collaboration-platform-administration` — mail, chat, meetings and file sharing,
+ where most of the organization's unstructured data actually lives
## The boundaries that cause arguments
diff --git a/plugins/pmo/skills/head-of-pmo/SKILL.md b/plugins/pmo/skills/head-of-pmo/SKILL.md
index d8c1545..aa6ed3f 100644
--- a/plugins/pmo/skills/head-of-pmo/SKILL.md
+++ b/plugins/pmo/skills/head-of-pmo/SKILL.md
@@ -26,6 +26,10 @@ it**. Teams own **how** the work gets done.
- `pmo:portfolio-governance` — intake, prioritization against real capacity, stage gates that can
stop things, and resource contention across projects
- `pmo:program-management` and `pmo:project-delivery` — the delivery disciplines themselves
+- `pmo:estimating-and-contingency` — how a defensible number is produced, and how much reserve
+ the portfolio actually needs
+- `pmo:schedule-development-and-analysis` — building a schedule from logic rather than dates, and
+ interrogating one you inherited
- `pmo:dependency-and-risk-management` — the seams between teams, where programs actually fail
- `pmo:benefits-realization` — whether the value claimed at approval ever appeared
- `pmo:change-and-adoption` — whether anyone uses what was delivered