From the ecosystem ROADMAP (§5, ref #3686). Wave-1 = tool repos (draw/3d green, tg pending its CodeQL TS fix). Wave-2 is the rest.
What
Run rig init --yes + a conservative AGENTS/CLAUDE slim + a harvest report on each wave-2 repo:
- Bots: ExpenseSyncBot, garage-band, summary-bot, esphome-ir, claude-p, diploma, sme-archiving-gc, talks, upwork.
- The ecosystem tools themselves: review-cli, rig-cli, agent-tools.
Per repo:
rig init --yes (CI gates + harness).
- Conservative AGENTS/CLAUDE slim — drop now-self-advertised generic rules, keep project specifics.
- Produce a harvest report (feeds the agent-tools harvest issue).
Why
The ecosystem's value compounds only when every repo is on the same gates/harness and the generic rules are de-duplicated into skills.
Acceptance
- Each wave-2 repo has a rig rollout PR (or direct commit for the tool repos that work on main).
- Each slim keeps project specifics, drops only skill-covered generic blocks.
- Harvest findings filed against the agent-tools harvest issue.
Note: enable repo security settings (#5) is a prerequisite for the gates to actually run per repo.
From the ecosystem ROADMAP (§5, ref #3686). Wave-1 = tool repos (draw/3d green, tg pending its CodeQL TS fix). Wave-2 is the rest.
What
Run
rig init --yes+ a conservative AGENTS/CLAUDE slim + a harvest report on each wave-2 repo:Per repo:
rig init --yes(CI gates + harness).Why
The ecosystem's value compounds only when every repo is on the same gates/harness and the generic rules are de-duplicated into skills.
Acceptance
Note: enable repo security settings (#5) is a prerequisite for the gates to actually run per repo.