alectivism Template skill. Fill in the [BRACKETED] placeholders with your organization's details — or paste your org context and ask Claude to populate them for you.
Asana Task Management — [YOUR ORGANIZATION]
Creating Tasks
Required Information
- Task name — clear, action-oriented (start with a verb)
- Project — which Asana project does this belong to?
- Assignee — who is responsible?
- Due date — when is it due?
Optional but Recommended
- Description — context, acceptance criteria, links
- Section — which section/column in the project board
- Tags — for cross-project tracking
- Dependencies — what needs to happen first
Task Naming Conventions
- Start with a verb: "Draft," "Review," "Send," "Create," "Update," "Schedule"
- Be specific: "Draft [PROGRAM] Q2 results summary for newsletter" not "Write thing"
- Include the deliverable: "Create speaker one-pager for [Name] — [Event]"
Common [YOUR ORGANIZATION] Projects
When creating tasks, consider which project they belong to:
- [Project 1 — e.g., CEO/Executive Worklist] — items for [executive name]'s attention
- [Project 2 — e.g., Marketing Calendar] — content and campaign work
- [Project 3 — e.g., Event: [Event Name]] — event planning and logistics
- [Project 4 — e.g., Program: [Program Name]] — ongoing program work
- [Project 5 — e.g., Ops / PMO] — cross-functional and operations tasks
- [Add your organization's key Asana projects]
Process
- Confirm task details (name, project, assignee, due date)
- Search for existing tasks to avoid duplicates
- Create the task with full context in the description field
- Confirm before creating — show the task details for approval
- Report back with the task link
Updating Tasks
- Search for the task first using keywords
- Show current status before making changes
- Confirm changes before applying
Asana Workspace
Your organization's Asana workspace: [YOUR ASANA WORKSPACE URL or name]