asana-task

Files (1)

• SKILL.md

SKILL.md (first lines)

# Asana Task Management — MMA

## 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"
- Be specific: "Draft CAP Q1 results summary for newsletter" not "Write thing"
- Include the deliverable: "Create POSSIBLE speaker one-pager for [Name]"

## Common MMA Projects
When creating tasks, consider which project they belong to:
- CEO Worklist (GS Worklist) — items for Greg Stuart's attention
- Think tank projects (ALTT, MATT, MOSTT, DATT)
- Event projects (POSSIBLE, CMO Summit, SMARTIES)
- Membership operations
- Marketing/Content calendar
- AI initiatives

## Process
1. Confirm task details (name, project, assignee, due date)
2. Search for existing tasks to avoid duplicates
3. Create the task with full context in description
4. **Confirm before creating** — show the task details for approval
5. 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

From alectivism/maven-template, MIT.

More from alectivism/maven-template