📋 Task Lifecycle
From idea to archive — the full journey of a work unit through the Agentic Hub.
Status Flow
| Status | Meaning | Who Sets It |
|---|---|---|
draft | Brain dump, not yet committed. ID prefix d- | Portal Inbox (auto) |
idea | Worth considering, needs shaping | Clara (classification) |
ready | Shaped and scoped, ready to be picked up | Clara or Adrian |
backlog | Prioritized and queued for work | Clara (align/focus) |
active | Currently being worked on | /task start |
done | Work complete, pending archive | /task done |
archived | Moved to archive, no longer active | /clara archive |
Task Commands
/task start <ID>
Begin Working on a Task
Creates the task folder at tasks/active/A{ID}-{slug}/, writes an initial README.md, records the start time, and PATCHes the D1 status to active.
What it does:
- Create
tasks/active/A{ID}-{slug}/directory - Write
README.mdwith task context from D1 - Record start time for velocity tracking
- PATCH task status to
activein D1 - Post session-start message to #dev channel
/task save
Mid-Session Checkpoint
Saves progress without closing the task. Commits current changes, updates the task README, but does NOT log velocity or mark as done.
When to use: Long sessions where you want to preserve progress before a break. The task remains active.
/task done
Complete a Task
The full wrap-up: commit, log, velocity entry, memory update, and status change to done.
What it does:
/task archive
Archive a Completed Task
Moves the task folder from tasks/active/ to tasks/archive/ and PATCHes D1 status to archived. Usually done by Clara, not manually.
/task spawn
Prepare Deferred Work Package
Creates a work package that can be executed later via Bifrost. Useful for breaking large tasks into autonomous sub-jobs that run without VS Code.
Task IDs
| Pattern | Example | Meaning |
|---|---|---|
A{number} | A94 | Committed task in the tech tree (Agentic workspace) |
d-{uuid} | d-a1b2c3 | Draft — not yet shaped into a real task |
Task Folder Structure
tasks/active/A94-portal-docs-expansion/ ├── README.md Task context, status, notes ├── plan.md Implementation plan (optional) └── ... Any working files for the task
The task folder is the agent's working space. It's created by /task start and moved to tasks/archive/ by /clara archive.
For Agents
GET /api/tasks) for task data — never grep local files. D1 is the source of truth. Use -DisableKeepAlive on all API calls.