Delivery Metrics

LinearB reports engineering delivery metrics like cycle time, deployment frequency, and pull request size across teams. A Beam agent reads the latest metric snapshots on a schedule, compares them to the baselines your leaders set, and posts a written summary to the right channel: calling out a team whose cycle time jumped or whose review depth dropped. It attaches the specific numbers behind each callout. Interpreting why a metric moved, or deciding on a process change in response, stays with the engineering leader, whom the agent notifies with the relevant figures for judgment.

Pull Request Workflow

LinearB watches pull requests as they move from open to merged, tracking review time and idle stages. A Beam agent reads PR activity, applies your team's rules, and acts on stalls: tagging a review that has waited past a threshold, noting oversized PRs that need splitting, or reminding an assigned reviewer. It records what it flagged for the daily digest. When a PR is contentious, blocks a release, or needs a judgment about merge readiness, the agent escalates to the team lead rather than forcing it through on its own.

Team Goals

LinearB lets engineering teams set goals against delivery metrics and shows progress toward them. A Beam agent checks goal progress on a cadence, reads current versus target values, and updates stakeholders using the reporting rules you define: noting goals that slipped, celebrating ones that hit target, or grouping laggards for the next retro. It compiles the figures into a plain progress note. Setting new goals, adjusting targets, or deciding whether a miss matters remains with the engineering manager, who receives the agent's summary for the discussion ahead.