What's wrong

A closed-won or closed-lost deal keeps carrying the tasks that existed to move it forward , the chase for a reply, the recap owed from a meeting, the response to a thread.

572 open tasks sit on closed deals today, across 52 accounts:

The 138 future-dated reactivations are deliberate work. The 388 overdue ones are residue.

Nothing cancels them: there is no stage-change handler anywhere in the codebase, and the one instruction that mentions the case tells the agenda agent the opposite , a terminal stage "is not a reason to cancel". That rule is right for deliberate reactivations and wrong for everything else, and it is stated without the distinction.

Where the rule lives, and why

assembleNextStepsPrompt, not the seeded next-steps body:

• a per-user document can be edited away , 20 of 61 active accounts have edited theirs
• next-steps runs on every event, so it fires when the deal actually closes rather than up to a day later, which is the agenda's cadence

What it says

Cancelled, never done. The work stopped being necessary; it did not happen. Recording it as done says the rep did something they did not do, and inflates the completion metric the task system is judged on.

Never cancelled, whatever the due date: reactivation, re-engagement, win-back, renewal, upsell, expansion, onboarding and customer-success work. Those are the path forward on a closed deal, not residue.

Defers to the user. The block says outright that a user's own next-steps instructions override it , a default, not a policy.

Verified

• tsc -b on @zero/server , clean
• vitest run over mastra/tools/task and mastra/routeHandlers , 246 passed, 2 skipped
• 4 new tests in next-steps-prompt.test.ts covering the cancel instruction, the done prohibition, every protected category by name, and the user-override clause

Not in scope

The 388 already-stranded tasks. This stops the accrual; a backfill is separate, and I'd rather run it after watching this behave.

🤖 Generated with Claude Code

Greptile Summary

The PR adds an always-present next-steps prompt rule that cancels obsolete deal-advancing tasks when a deal closes while preserving reactivation and post-close work.

• Registers the cleanup rule in the assembled prompt’s block map.
• Adds prompt guidance for cancellation, protected categories, and user overrides.
• Adds tests covering the new instruction text and exemptions.

Confidence Score: 4/5

The conflicting seeded and terminal-stage instructions should be reconciled before merging so closed-lost deals reliably shed obsolete advancing tasks.

The assembled prompt can simultaneously tell the agent that closed-lost is not grounds for closing a task and that differing next-steps instructions override the new cleanup rule, undermining the feature for accounts using the seeded instructions.

Files Needing Attention: apps/server/src/mastra/tools/task/next-steps-prompt.ts

Important Files Changed

Flowchart