Asana Task Triage Agent with OpenCode
Triage here is a short chain that repeats: read the task properly, place it in a section, give it an owner, ask once for the deliverable or the real deadline. It is a focused loop with a clear end, and pointing a light agent at exactly one loop is what OpenCode is for. The model behind it stays yours to choose.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Redraw the pricing page for the Q3 brand update
Eassigned to Emeka Balogun
The pricing page needs redrawing in the new brand by 5 August so it goes out with the Q3 announcement. Figma file and the approved palette are linked in the description. Copy is final and Leena has signed it off.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Asana
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Triage rules
Your triage rules - which section each kind of task belongs in, what a task has to contain before work can start on it, and what makes something urgent enough to interrupt a person.
Team map
Each kind of work matched to the Asana teammate who owns it, and the fallback owner for tasks that fit none of them.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
One loop, clearly bounded
There is no open ended exploration in this job, which is where a lighter harness would struggle. It reads one task and writes three things.
Choose the model per project
A design requests project with a two line rulebook and a legal intake project with a page of rules can run the same template on different models.
Before you fork
How do I see what it did last week?
In two places. Asana holds most of it, since every placement leaves a comment naming the section, the owner and what was missing, and the task history records the move. NoClick keeps the run history alongside, so you can open one run and see which tools were called and what came back. If a task was placed oddly, both halves of the story survive.
Run it with a different agent
Put Asana Task Triage Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.