Turn results into improvement actions
Create an action from a run or through an agent, complete it, link an external tracker, and check for duplicates first
An action is the concrete next step a health check earns — a title, and eventually an owner and a due date, tracked until it's done.
Creating one
Once a run reaches Discuss (or after it's closed), the "Turn it into an action" box on the run page captures a title and an optional due date on the spot, so an idea from a live discussion doesn't get lost. Before it's created, SquadBear checks the team's last 180 days of actions for a close semantic match; if it finds one, it asks whether to add this as a new action anyway or keep the existing one instead of creating a silent duplicate. Assign or change the owner afterward from the pencil-edit on the action row, which also holds priority, status and a longer description.
You don't need a run at all: New action in the Team Health → Actions header opens the same editor in create mode. Pick the team, give it a title, and optionally set an owner, due date, priority and description — it's filed straight away as a manual action. An agent can do the same directly, title through priority in one call.
The Actions list
Team Health → Actions lists every action the viewer can see — everything, for an admin; otherwise their teams' actions plus anything they personally own — filterable by team, status and owner, with an "Overdue only" checkbox. Its New action button (above) files one without leaving the page. Tick an action's checkbox here to complete it: any member of the action's team can, not only its owner. On the run it came from, only a facilitator gets that checkbox.
Linking an external tracker
After pushing an action to Jira, GitHub or another tracker through that tool's own MCP connection, an agent can record the resulting issue key or URL against the action to close the loop between the two systems. There's no badge for it on the action row today — the reference round-trips through the API and MCP, ready for a future UI to show it.
Before you create a duplicate
The same semantic check the run page runs on submit is also callable directly: given a team and some draft text, it returns up to three existing actions — open, in progress or done, from the last six months — that read similarly, each with its status, owner and date. Worth a look before filing a standalone action, not just a run-sourced one.
Nothing in the app lines a dimension's trend up against absence — an agent can. Given a team's closed-run history, it walks it period by period against approved leave days per member in the same window, flagging inverse movement when a dimension falls while absence rises, and leading decline when people's felt-direction votes turned negative before the average did. Correlation, not causation, and it has no page of its own.
Worked example
Marta ticks "Rebalance Platform's on-call rotation" done on the Actions list. When Workload dips again after Platform's next Pulse 5 run, she doesn't file a new action blind: she asks her agent to check for anything similar first, and to see whether the dip lines up with rising absence, before deciding a fresh action is worth creating.