Use cases
Engineering & SRE

Sprint blockers and how they were resolved

Every blocker mentioned in standup or thread, and the resolution path.

Best for
Retro prep
Primitives
  • Blockers
  • Interactions
  • Owners
Side by side

Token Usage, with and without Sentra

~76k tokens saved63% less work for the agent

Without Sentra
~120k tokens
With Sentra
~44k tokens
Claude (without Sentra)
  1. Pull every standup transcript, threads in #eng channels, 1:1 notes, and ticket comments in the sprint window.
  2. Read each for blocker-shaped language ('blocked on', 'waiting for', 'can't ship until').
  3. For each blocker, identify the affected service or project by reading context.
  4. Track resolution path — search subsequent threads for the unblocking moment.
  5. Compute time-to-unblock manually from timestamps.
  6. Cluster recurring root causes by re-reading and judging.
  7. Compose the table and root-cause ranking.
~120k tokens
Claude + Sentra
  1. Pull Interactions in the sprint window where Sentra extracted a Blocker event.
  2. Each Blocker carries: typed Actor raiser, affected Value Object, resolution path, owning Actor, time-to-unblock, shipped or rolled.
  3. Cluster recurring root causes via Sentra's learned Theme taxonomy.
  4. Compose the table and the closing recommendation.
~44k tokens
Agent prompt
You are preparing a retro on sprint {{sprint_id}}.

Using Sentra:

1. Pull entities around the sprint window where Sentra extracted a Blocker — standups, threads, 1:1s, ticket comments.
2. For each Blocker, return: who raised it, when, the affected Value Object (service / feature / project), the resolution path, the owner who unblocked it, the time-to-unblock, and whether it shipped resolved or rolled to next sprint.
3. Cluster recurring root causes (dependency wait, missing context, unclear scope, broken tooling, etc.).

Output:

- Table of every Blocker with the columns above.
- Top three recurring root causes with the cluster size.
- One paragraph: the single change that would have prevented the most pain this sprint.

Sentralize your company.

Remember what matters.

Preferences

Subprocessors include Amazon Web Services, GitHub, Slack, Google Cloud Platform, and OpenAI.

© 2026 Dynamis Labs Inc. All rights reserved.