Skip to content

Feature release

effortdiagnosis

Know if your team's effort is seeing the light of day

Eugenio Sanchez

1 min read

Not all work gets shipped. This is more true now than ever, with agents drafting PRs automatically. Discarded work is a healthy part of many agentic workflows, but it should be in its own category when analyzing the work of your team.

Now you can do this in Mesmer, whether working directly with the platform’s assistant or with MCP. You can break down all work into released, not released, and discarded. Discarded work includes all closed, abandoned, or superseded PRs.

Since discarded work is still work, it will still be considered in the platform’s Overview and Statistics graphs.

Mesmer contributions list showing six pull requests. Each row carries a status badge — three are marked Discarded (red dot) and three are marked Agentic — alongside the repository (monorepo or design), PR number, work category (Performance, Feature, Documentation, Chore, or Refactor), an effort score, and how long ago it landed. Discarded PRs sit inline with the rest but are clearly labeled.
Work in Mesmer broken down by status. Discarded contributions — closed, abandoned, or superseded PRs — are labeled inline alongside released work, each still carrying its category and effort score.

What this unlocks#

  • Every contribution is now either released, not released, or discarded, which makes discarded work useful at every level.
  • You can use discarded work as the center of your analysis to see where it concentrates, or instead look at individuals or teams with discarded work as one of many datapoints.
  • Dig deeper to the contribution level, to understand what type of work is getting discarded.