Overview
| Command | Description | Cost |
|---|
naive tasks list | List tasks with optional filters | Free |
naive tasks create <title> | Create a new task | Free |
naive tasks show <id> | Show full task details | Free |
naive tasks run <id> | Trigger a worker to execute a specific task | Free |
naive tasks complete <id> | Mark a task as completed | Free |
naive tasks block <id> | Mark a task as blocked | Free |
naive tasks unblock <id> | Remove blocked status | Free |
naive tasks comment <id> <text> | Add a comment to a task | Free |
naive tasks dispatch | Auto-assign pending tasks to employees | Free |
naive tasks stats | Show board statistics | Free |
How It Works
Tasks are the unit of work in the naive kanban system. The CEO creates objectives, which are broken into tasks, which are assigned to employees. Tasks flow through statuses: ready → running → done (or blocked).
The embedded kanban dispatcher in the Hermes gateway automatically spawns worker processes for assigned tasks every 15 seconds. Workers call kanban_complete() when done.
List Tasks
naive tasks list
naive tasks list --status running
naive tasks list --assignee "Dev Diana"
naive tasks list --objective obj-abc-123
Options
| Flag | Description |
|---|
--status <status> | Filter by: ready, running, done, blocked |
--assignee <agent> | Filter by assignee name |
--objective <id> | Filter by parent objective ID |
Create a Task
naive tasks create "Write blog post about AI trends"
naive tasks create "Deploy landing page" --assignee "Dev Diana" --priority high
naive tasks create "Research competitors" --description "Find top 5 competitors and analyze features" --objective obj-abc-123
Options
| Flag | Description |
|---|
--assignee <name> | Assign to an employee by name (e.g., --assignee "Jordan Kim"). Must match the employee name exactly. |
--objective <id> | Link to a parent objective |
--priority <level> | low, medium (default), high, or critical |
--description <text> | Detailed task description (strongly recommended — workers need this to understand assignments) |
The title is a positional argument (no --title flag needed). Task IDs can be either standard UUIDs or Hermes task IDs (e.g., t_a2a1ae0c) — both formats are accepted by all task commands.
Complete a Task
naive tasks complete abc-123 --summary "Blog post published at /blog/ai-trends"
naive tasks complete abc-123 --metadata '{"url": "https://example.com"}'
Options
| Flag | Description |
|---|
--summary <text> | Completion summary |
--metadata <json> | JSON metadata to attach |
Block / Unblock
naive tasks block abc-123 --reason "Waiting for domain DNS propagation"
naive tasks unblock abc-123
naive tasks comment abc-123 "Added SEO meta tags to the blog post"
Run a Task
Directly trigger a worker to start executing a specific assigned task. The task must already have an assignee.
naive tasks run abc-123
naive tasks run t_a2a1ae0c
The task must be assigned to an employee and not be in done or blocked status. If unassigned, use naive tasks create with --assignee or PATCH the task first.
Dispatch Tasks
Auto-assign pending tasks to available employees based on skills and capacity.
Board Statistics
Returns task counts by status, employee utilization, and blocked task summary.
Typical Workflow
# 1. Create a task with a description
naive tasks create "Write blog post" --assignee "Content Casey" --description "Write a 1500-word post about AI trends in 2026" --priority high
# 2. Monitor active work
naive tasks list --status running
# 3. Add guidance
naive tasks comment <id> "Add SEO keywords"
# 4. Complete
naive tasks complete <id> --summary "Published to blog"
# 5. Review board health
naive tasks stats
