Agent Ops Club by Reinventing.AI

Oversight and strategy

Chief of Staff

Know which work ran, which stopped, and what needs you.

Watches every other employee and tells you what needs attention.

Free with an accountMIT licensed
  • 2 weekdays
  • 3 weekly
  • 2 monthly
Chief of Staff with the tools of the role

One routine, start to finish

What lands when the Chief of Staff runs.

01

Check every employee.

As soon as several employees run on schedules, oversight becomes a role of its own. The Chief of Staff reads the fleet state and run records, distinguishes an intentional pause from a silent stop, and prepares a dossier for the problem that needs attention.

02

Find what stopped. Work out why.

Decision and metric reviews connect that operational picture to your business priorities. You get a brief with the evidence and next decision, rather than having to open every employee folder to find out whether the week is moving.

03

Write the brief.

It observes the other employees and does not rewrite their files. Oversight identifies a decision; it does not grant itself permission to change another role or release a channel.

A sample run, built from the kit's own routine. Nothing here is a customer's data.

Who is this for?

Three people the Chief of Staff was built for.

  • Founder running several AI Employees

    One morning brief that says what needs you, across every role.

  • Team with a growing scheduled workflow

    Paused, failed and missed runs told apart before you ask.

  • Provider supervising a client's employees

    One view of every employee you run for every client.

The 7 scheduled routines.

The cadence is part of the role. Each one owns a defined piece of work.

  • Fleet reconcile

    Walks every AI Employee on this machine, strictly read only, and classifies each routine as running, stopped loudly, stopped silently, or paused.

    Weekdays
  • Fault dossier

    Takes the top open fault and turns it into a page you can act on in a minute, ending in one paste-ready correction line and the exact path it belongs in.

    Weekdays
  • Market sweep

    Works its own watchlist through one contiguous browser phase and captures one dated observation per real change, with a verbatim quote and the URL.

    Weekly
  • Metrics review

    Scores the fleet and the business with a source beside every number, citing the Employee that owns a metric rather than recomputing it.

    Weekly
  • Decision brief

    Picks three moves, argues both sides of each with a citation in every clause, and argues against its own top recommendation last.

    Weekly
  • Charter and fleet audit

    First run researches the business, discovers the Employees on this machine, writes the map and the charter, and registers seven jobs.

    Monthly
  • Decision review

    Folds the decision ledger, scores its own judgement against the metric files that measured it, and retires a move nobody ever accepted.

    Monthly
More about the Chief of Staff: outputs, connections, setup and related material

As soon as several employees run on schedules, oversight becomes a role of its own. The Chief of Staff reads the fleet state and run records, distinguishes an intentional pause from a silent stop, and prepares a dossier for the problem that needs attention.

Decision and metric reviews connect that operational picture to your business priorities. You get a brief with the evidence and next decision, rather than having to open every employee folder to find out whether the week is moving.

Best fit: Founders operating several AI Employees, teams coordinating a growing scheduled workflow, and providers supervising a client employee fleet.

The work you can review

  • Fleet audits and a reconciled operating picture
  • Fault dossiers with evidence and a likely cause
  • Decision briefs and a decision register
  • Metrics and strategy reviews against your charter

Set up the first week

Confirm the charter and which employees are in scope. Check that intentional pauses and run records are readable, then review the first brief for useful priorities and enough evidence to act.

Choose the role in the Club install prompt builder, extract the kit to a local folder, and ask your agent to install it. The setup guide explains local and cloud harnesses. Your first week is supervision: inspect the output and correct the standard before widening permissions.

Accounts and connections

Mail, meetings, documents, the board and the books are read through their own connectors, so the Thursday review cites a route instead of a screenshot. Connect only the services you use and the installed kit requires; access and costs depend on your accounts.