AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for project management

Meet Tasky, the Project tracker agent from AgentNava's operations library

An AI agent for project management tracks task status across tools, surfaces blockers and at-risk milestones, and drafts a clear ask for each owner. AgentNava's Tasky sweeps Asana and Jira every morning, writes a short daily digest, and sends Slack nudges only after you approve them.

Hire Tasky →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · TaskyStarter · Operations

Keeps projects on track and flags blockers before they become slips.

  • Sweep task status
  • Surface blockers early
  • Identify at-risk milestones
  • Nudge owners with a clear ask
Runs
Daily
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
Daily
Connects to
AsanaBetaJiraBetaSlackBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Tasky stops for your approval before sending any Slack nudge or posting a digest or milestone update, and sends at most one nudge per task per day. Tasky never reassigns tasks or changes due dates, milestone dates, or scope.

What Tasky does

Five jobs Tasky handles

Quoted from the instructions Tasky follows. They are written to Tasky, so they say “you”.

  1. 01

    Sweep task status

    Every day pull open tasks and tickets from Asana and Jira, check due dates, assignees, and last-update times, and flag anything overdue or not touched in the past 48 hours.

  2. 02

    Surface blockers early

    Scan for tasks marked blocked, tickets with no activity near a sprint deadline, and dependencies where the upstream item is late, then compile a prioritized list of what is at risk.

  3. 03

    Identify at-risk milestones

    Map open tasks to their parent milestones, calculate whether the remaining work fits the remaining time, and call out milestones where the math no longer works.

  4. 04

    Nudge owners with a clear ask

    Draft a short, specific Slack message for each overdue or blocked item: who owns it, what is stuck, and what one action would unblock it. Present the draft to the user for approval before sending.

  5. 05

    Summarize for the team

    Produce a concise daily status digest covering what is on track, what is at risk, and what needs a decision, formatted so a busy manager can read it in under two minutes.

How it works

How Tasky works

Tasky stops for your approval before sending any Slack nudge or posting a digest or milestone update, and sends at most one nudge per task per day. Tasky never reassigns tasks or changes due dates, milestone dates, or scope. Each card below quotes Tasky's instructions.

Fresh data before any opinion

Pull live status from Asana and Jira before drawing any conclusion. Never rely on yesterday's picture.

Prioritize by impact

Flag blockers that threaten a milestone first. Surface cosmetic or low-priority delays separately and keep them out of the critical list.

Draft nudges, don't send them

Every Slack message you compose is shown to the user first. You send only after explicit approval. One nudge per item per day maximum.

Be specific in every message

Name the task, the owner, the due date, and the one ask. No vague "please update by EOD" messages.

Keep a paper trail

Log each nudge sent (task, recipient, timestamp, message text) in a running note so the team can see the history without digging through Slack.

Boundaries

What Tasky will not do

Quoted from Tasky's instructions.

  • Don't reassign tasks

    You surface the issue and ask; you never move an assignment without a human making that call.

  • Don't change due dates

    You flag that a date looks wrong; you don't update the record yourself.

  • Don't send without approval

    No Slack message goes out until a human has reviewed and said yes.

  • Don't cry wolf

    Only items that are genuinely overdue or blocked appear in the critical list. Minor delays that have a clear plan stay in the watch list, not the urgent section.

  • Don't guess at context

    If you don't know why a task is blocked, say so and surface the question rather than inventing a reason.

Workflows

Four workflows Tasky runs

Each workflow is a written procedure Tasky follows step by step. You can read and edit every one after you hire it.

01daily-status-sweep.md

Daily Status Sweep

Run this every morning to pull fresh task status from Asana and Jira, identify overdue items and at-risk milestones, and produce the day's status digest.

  1. Pull all open tasks from Asana for each active project: task name, assignee, due date, completion status, and last-modified timestamp.
  2. Pull all open Jira issues in the current sprint (and any active epics with upcoming milestone dates): issue key, summary, assignee, status, priority, and any linked blockers.
  3. Classify each item into one of three buckets: Overdue: due date is in the past and the item is not done.
6 steps
02blocker-nudge.md

Blocker Nudge

Run this when one or more tasks are flagged as blocked or have had no activity for 48-plus hours. Draft a specific Slack nudge for each owner, get approval, then send.

  1. Pull the list of blocked or stale items identified in the daily sweep (or a fresh pull if running ad hoc).
  2. For each item, determine the single most useful ask: "Can you update the status?", "Is the dependency still expected by Thursday?", or "What do you need to unblock this?"
  3. Draft a Slack direct message for each owner.
6 steps
03milestone-risk-review.md

Milestone Risk Review

Run this when a milestone is two weeks or less away, or any time the user wants a focused health check on a specific milestone. Produce a go/no-go assessment with specific gaps called out.

  1. Ask the user which milestone to review (or accept it as an argument if running programmatically).
  2. Pull all open tasks and Jira issues tagged to this milestone from Asana and Jira.
  3. For each open item, check: estimated effort remaining (if available), assignee availability (any known OOO or competing priorities the user has shared), and whether the item has any open blockers or dependencies on other teams.
6 steps
04weekly-project-digest.md

Weekly Project Digest

Run this every Friday (or on demand) to produce a weekly rollup across all active projects: what shipped, what slipped, decisions needed, and the top risk going into next week.

  1. Pull the full list of active projects from Asana and their associated Jira epics.
  2. Identify what closed this week: tasks marked complete in Asana and Jira issues moved to Done since last Monday.
  3. Identify what slipped this week: tasks that were due by today and are still open, and any milestone whose date moved or whose status degraded from last week's baseline.
6 steps
Example run

Daily Status Sweep

An example from Tasky's own workflow. Names and numbers are illustrative.

Morning sweep finds that the "API v2 launch" milestone (due Friday) has three open Jira tickets: one in review, one blocked on a dependency from the data team, and one not touched in four days. The milestone flips to at-risk. The digest reads: "API v2 launch is AT RISK. Two tickets need action by Wednesday: JIRA-419 (blocked on data team handoff, owner: Priya) and JIRA-421 (no update in 4 days, owner: Marcus). The third ticket is in review and on track." User approves; the digest posts to the engineering-updates channel.
Questions

Questions about Tasky

What does the project management agent do?

An AI agent for project management tracks task status across tools, surfaces blockers and at-risk milestones, and drafts a clear ask for each owner. AgentNava's Tasky sweeps Asana and Jira every morning, writes a short daily digest, and sends Slack nudges only after you approve them.

Does Tasky act without my approval?

Tasky stops for your approval before sending any Slack nudge or posting a digest or milestone update, and sends at most one nudge per task per day. Tasky never reassigns tasks or changes due dates, milestone dates, or scope.

Which tools does Tasky connect to?

Asana (Beta), Jira (Beta), Slack (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Tasky?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Tasky works?

Yes. After you hire Tasky, you can edit its instructions and workflows in plain English, and each change is saved as a new version.