Templates

Delivery

Unblock work fast

Use Template

By Nalvin

Use Template

Description

Nalvin helps you move work forward by finding the biggest blockers and stalled items in your active scope and summarizing who needs to do what next. It pulls status, ownership, and activity signals from your project system, highlights the highest-risk items, and suggests concrete next actions without guessing missing context.

Supported Integrations

Templates are flexible by default. Nalvin automatically picks the right integrations based on what you’ve connected.

Asana

ClickUp

Monday

Trello

Shortcut

Linear

Microsoft Teams

Jira

Slack

How to best use this template

Below are a few tips & tricks from the Nalvin team to get the most out of this template.

Choose a tight scope

Start with one project, epic, or sprint so the output is immediately actionable. You can level this up by saving multiple scopes (e.g., “Platform” and “Mobile”) and running them separately.

Define what “blocked” means

Blocked can be an explicit status, a dependency tag, or lack of movement. Tell Nalvin which signals matter most in your workflow so it doesn’t miss real blockers.

Ask for the “next action owner”

When ownership is unclear, have Nalvin call it out explicitly and suggest who should confirm it. This prevents ambiguous items from staying stuck indefinitely.

Use evidence, not assumptions

Have Nalvin cite the signal behind each blocker (status, age, dependency mention). If evidence is thin, it should say so and propose the smallest follow-up question.

Convert blockers into actions

You can level this up by asking Nalvin to draft a quick unblock message or create a follow-up task, but only after you approve the targets and text.

Choose a tight scope

Start with one project, epic, or sprint so the output is immediately actionable. You can level this up by saving multiple scopes (e.g., “Platform” and “Mobile”) and running them separately.

Define what “blocked” means

Blocked can be an explicit status, a dependency tag, or lack of movement. Tell Nalvin which signals matter most in your workflow so it doesn’t miss real blockers.

Ask for the “next action owner”

When ownership is unclear, have Nalvin call it out explicitly and suggest who should confirm it. This prevents ambiguous items from staying stuck indefinitely.

Use evidence, not assumptions

Have Nalvin cite the signal behind each blocker (status, age, dependency mention). If evidence is thin, it should say so and propose the smallest follow-up question.

Convert blockers into actions

You can level this up by asking Nalvin to draft a quick unblock message or create a follow-up task, but only after you approve the targets and text.