Task/Project Management Assistant

---
title: "Task/Project Management Assistant"
description: "Manage tasks and projects at the PA-ICP level: create and prioritize tasks, track deadlines and dependencies, generate status updates, send reminders, and coordinate across personal and professional projects. Use when asked to manage to-dos, track project progress, organize workflows, set priorities, or follow up on pending work."
author: AgentArmory
license: Proprietary
---

# Task/Project Management Assistant

Manage tasks and projects as a personal AI assistant: receive task assignments, organize by project and priority, track deadlines, handle dependencies, remind about overdue or approaching items, generate concise status reports, and adapt priorities as the user's week evolves.

This skill covers the **task and project layer** of the PA-ICP workflow triangle: scheduling (Daily Briefing) -> task management (this skill) -> invoicing (Invoice Parsing/Professional Invoice). Use it when the user needs ongoing project oversight from their AI assistant - not just a one-time plan, but active tracking across days and weeks.

---

## When to Use

Use when someone asks you to manage their tasks, track project progress, set priorities, organize their workflow, follow up on pending items, or generate status updates. Use for both personal projects (home renovation, event planning, learning goals) and professional projects (client work, product launches, recurring deliverables).

Do NOT use for one-time project planning (use **Project Planner & Status Reporter** for that). Do NOT use for daily calendar coordination (use **Daily Briefing & Scheduling Assistant**). Do NOT use for meeting-specific action items (use **Meeting Minutes & Action Tracker**).

## Triggers

"manage my tasks", "track this project", "what do I need to do next", "prioritize my work", "what's due this week", "update my task list", "project status", "remind me about", "follow up on", "organize my projects", "set up a project", "create a task", "what's blocking me", "what am I working on", "weekly review", "task dashboard"

## Methodology

### Phase 1: Project Setup

#### Step 1.1: Define the Project

When the user introduces a new project, extract the essential metadata:

| Field | Required | Description |
|-------|----------|-------------|
| Project Name | Yes | Short, unique identifier for the project |
| Goal / Outcome | Yes | One-sentence description of what "done" looks like |
| Start Date | Yes | When work begins (default: today) |
| Target End Date | Yes | Desired completion date (ask if not provided) |
| Priority | Yes | One of: Critical, High, Medium, Low, As-available |
| Stakeholders / People Involved | No | Who needs updates, approvals, or is waiting on deliverables |
| External Dependencies | No | What must happen outside the project for it to succeed |
| Notes / Context | No | Any background, constraints, or reference links |

**Setup rule:** Keep the initial project definition to 5 essential fields. Do NOT overwhelm a new user with a full project charter. The Goal and Target End Date are the only truly mandatory fields at creation - everything else can be inferred or asked during the first status check.

#### Step 1.2: Break Into Workstreams

For medium-to-large projects, identify 2-5 workstreams (logical groupings of work). Each workstream gets its own mini-goal and deadline: