# Task System

> Create, manage, and complete tasks in cortextOS. Use when starting significant work, tracking progress, or completing deliverables.

- Skill: `grandamenium/task-system` (Agent Skill)
- Install (CLI): `npx skillmds@latest add grandamenium/task-system`
- Raw SKILL.md: https://api.skillmd.com/api/skills/grandamenium/task-system/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: grandamenium (https://skillmd.com/u/grandamenium)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/grandamenium/task-system

---


# Task System

Every significant piece of work must have a corresponding task. Tasks enable coordination, accountability, and measurable progress.

## Task Types

- **Agent tasks** - Work executed autonomously by the assigned agent
- **Human tasks** - Requires human decision, input, or approval (assigned_to=human)

## Lifecycle

### 1. Create (BEFORE starting work)
```bash
cortextos bus create-task \
  "<title>" "<description>" [assignee] [priority] [project]
```

### 2. Mark in progress
```bash
cortextos bus update-task <task_id> in_progress
```

### 3. Execute the work

### 4. Complete
```bash
cortextos bus complete-task <task_id> "[output summary]"
```

### 5. Log KPI (if measurable)
```bash
cortextos bus log-event action task_completed info \
  '{"task_id":"ID","kpi_key":"metric_name","value":1}'
```

## The `needs_approval` Field

**true** - external actions: sending emails, merging PRs, deploying, public announcements
**false** - internal work: research, drafts, feature branches, testing

Tasks with `needs_approval: true` create an approval item that must be reviewed before executing external actions.

## Script Reference

| Action | Command |
|--------|---------|
| Create | `cortextos bus create-task "<title>" "<desc>" [assignee] [priority] [project]` |
| List | `cortextos bus list-tasks [--status S] [--agent A] [--priority P]` |
| Update | `cortextos bus update-task <id> <status> [note]` |
| Complete | `cortextos bus complete-task <id> "[summary]"` |
| Log event | `cortextos bus log-event <category> <event> <severity> '[json]'` |

**Statuses:** pending, in_progress, blocked, completed

**Priorities:** high, normal, low

## Best Practices

- **Always create before starting** - ensures tracking and coordination
- **Be specific** - clear titles, descriptions with success criteria
- **Complete thoroughly** - include what was accomplished and where outputs are
- **Log KPIs** - when work advances a measurable goal