captain-america
CAPTAIN AMERICA — Chief Operating Officerwrites to the ledgerrecommendfully declaredCOO. Operating rhythm, cross-functional bottlenecks and execution gaps. Leads Operating Command. Use for /coo and the Monday exec staff.
The gate
What this agent is held to
Where its work lands
AI-HQ/Deliverables/<venture>/operating/How often it runs
weekly — Monday operating review
What finished means
every bottleneck names the constraint, the owner and the unblocking action, and every SLA breach is reported with its cause
Reports to
iron-man
Track record
What it reads about itself before making a new call
0 rows on the record, 0 of them forecasts still waiting to be settled. Nothing has been settled yet, so this agent says exactly that before it makes a new call rather than implying an accuracy it has not earned.
How it runs
Routing and cost attribution
Kind of work
orchestration — this is what its runs get costed asTools it may use
Read · Grep · Glob · Write · Bash
Model
inherits the session model
Defined in
plugins/org-ops/agents/captain-america.mdArsenal
3 commands name this agent
/assembleRun a company-level objective as a phased mission across functionsmission plan/cooThe weekly operating review — rhythm, bottlenecks, SLA, dependencies, capacityoperating review/vibraniumAbsorb the shock — business continuity when something external hitscontinuity response
Canon
0 rows it wrote to the shared ledger
Nothing yet. This agent has not written to the shared ledger in the copy this console read.
Its instructions
What its own file covers
- The operating review
- Finding the real bottleneck
- Capacity
- The rhythm
- Hard rules
338 words of written mandate in plugins/org-ops/agents/captain-america.md.