---
name: external-pm
description: >
  Manage tasks and projects in external providers: Linear, Asana, Notion, Jira, Monday.com via mcpportedencom MCP. Use for boards, items, comments, status updates, creation/deletion. Always discover providers and boards first. Route here from task-orchestrator for team/PM tool work.
---

# External Project Management Skill

Specialist for connected task providers (Linear, Asana, Notion, Jira Cloud, Monday, etc.).

## When to Use

- User mentions specific tools: "my Linear tasks", "create in Asana", "update this Notion page as task"
- Team project work, sprints, issues, client deliverables
- Anything requiring board/project structure, statuses, assignees, cycles

## Core Tools (mcpportedencom)

- `mcpportedencom__tasks_list_providers` — See connected systems (call first)
- `mcpportedencom__tasks_list_boards` — List projects/boards
- `mcpportedencom__tasks_get_board` — Details on groups, columns, fields (required before create/update)
- `mcpportedencom__tasks_list_items` — List tasks with filters (status, query, groupId)
- Create/update/delete/comment tools (use board schema for valid fields)
- Notion-specific: `mcpportedencom__tasks_append_blocks`

## Workflow

1. **Discovery**:
   - list_providers
   - list_boards (with provider if multiple)
   - get_board for the chosen boardId to learn valid statuses/groups/fields

2. **List work**:
   - list_items with boardId, optional filters (status, query, groupId, limit)

3. **Create item**:
   - Use board fields. Set title, description, status, etc.
   - For Notion, consider appending rich blocks later.

4. **Update**:
   - Use itemId + provider + updated fields from board schema.

5. **Comments / Details**:
   - list_comments, append_blocks (Notion)

6. **Cleanup**:
   - delete_item (archives in Notion, permanent elsewhere)

## Best Practices

- Never guess IDs or status values — fetch board first.
- Use exact provider codes (LINEAR, ASANA, NOTION, JIRA_CLOUD, MONDAY).
- For search: use query param or status filters.
- Link tasks to plans/PRs in descriptions.
- When multiple providers, always pass "provider" param.

## Integration

- Called by `task-orchestrator`.
- **Project plans**: After `generate-project-plan`, push the PR Plan items into boards (e.g., create Linear issues for each PR with fields from the plan).
- **lvlltd-launch-pack**: Create tasks for each step of the launch (x402 model, crypto plan, reputation reports, etc.) in the appropriate board. Track launch progress.
- **RSEO**: Log evolution plans and improvement tasks into external PM for review/collaboration.
- **Agent orchestration**: Assign tasks to agents, track completion. Use with `dispatching-parallel-agents` for parallel work across providers.
- **GitHub sync**: Link PRs/issues to external tasks.
- Feed status back to `todo-prioritizer` or scheduled-tasks for personal alerts.

## Examples

**Show open Linear tasks:**
list_providers → list_boards (provider=LINEAR) → list_items (boardId=..., status="In Progress")

**Create task in Asana:**
get_board → create item with title, description, status from schema.

Always list first, confirm before destructive actions (delete).