Use casesEngineering & 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
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.