| name | asana-update-project |
| description | Use when you need to summarize active and recently completed Asana project work into a clear project update comment with blockers and next steps. |
Asana Update Project
Overview
Build a concise, comment-ready project update from Asana MCP data: completed work, in-progress items, blockers, and next steps.
Required Workflow
- Interview the user for project context and update details.
- Confirm project and reporting window.
- Resolve target project via Asana MCP.
- Retrieve tasks we are currently working on and recently completed tasks.
- Reconcile MCP task data with user-reported updates.
- Classify results into
Completed, In progress, Risks/blocks, and Next 7 days.
- Produce a comment-ready summary suitable for posting in Asana.
Interview Workflow
Before drafting the update, ask targeted questions to capture:
- What was completed in the reporting window (with outcomes/impact)
- What is currently in progress (with next milestone/date)
- Current risks and blockers (owner and unblock action)
- Any priority changes for the next 7 days
If details are unclear or incomplete, ask follow-up questions until each section has enough context to produce a high-quality update.
Clarifying Questions
Ask when missing:
- Project name/workspace
- Reporting window (for example: last 7 days)
- "We" owner definition (assignee(s), team, or tag)
- Preferred verbosity (brief vs detailed)
- Completed outcomes and business impact
- In-progress status and next milestone
- Risks, blockers, and who owns each unblock action
Classification Rules
- Completed: Finished within reporting window.
- In progress: Actively worked on, not complete.
- Risks/blocks: Blocked tasks, slipped due dates, or dependencies.
- Next 7 days: Planned priorities and likely milestones.
Do not invent outcomes. If evidence is missing, call it out explicitly.
Output Format
## Project update (<date range>)
### Completed
- <task>: <outcome/impact>
### In progress
- <task>: <current status> | Next milestone: <date or checkpoint>
### Risks/blocks
- <task>: <blocker> | Owner: <name> | Unblock action: <action>
### Next 7 days
- <priority task and intended result>
Quality Bar
- Keep updates concise and specific.
- Include impact, not only activity.
- Include owners and explicit next actions for risks.
- Ensure output can be pasted directly into Asana comments.
Completion Checklist
