Skip to main content

Team Lead Guide

Workloom is for teams that already feel the cost of duplicated AI agent setup: instructions drift across repos, provider files disagree, and CI cannot prove which guidance developers are actually using.

What You Get Today​

  • A local CLI proof that package assets can render to provider files.
  • A fixture registry boundary shaped for future hosted replacement.
  • CI-style sync --check exits for clean, drifted, and policy-denied states.
  • Documentation and ADRs that explain why Workloom is package management, not folder mirroring.

What To Ask Before Adoption​

  1. Which AI provider files should be committed and reviewed?
  2. Which provider settings are local-only for developers?
  3. Which trust surfaces must be blocked until security review?
  4. Which repos should be the first pilot targets?
  5. What would CI need to enforce before this is valuable?

Start with one repo and one baseline package:

pnpm wl render --workspace fixtures/workspaces/simple-workspace.json --dry-run
pnpm wl sync --check --workspace fixtures/workspaces/simple-workspace.json

Then evaluate the committed Copilot projection flow:

pnpm wl render --workspace fixtures/workspaces/committed-copilot-projection.json --dry-run
pnpm wl sync --workspace fixtures/workspaces/committed-copilot-projection.json --approve-local

Why This Matters​

AI workflow assets are becoming operational infrastructure. Treating them as copy-pasted markdown makes review, rollout, rollback, and drift detection harder than it needs to be. Workloom gives teams a path toward package versions, desired state, provider-aware rendering, and CI enforcement.