Tasks and cards
In dreeft, a task is represented by a card on the Kanban board. The card’s column and status tell you where it is in the workflow and whether a human decision is needed.
Card fields
- Title — short name; visible on the board.
- Description — the main briefing for agents.
- Column — current queue; determines which agent may run.
- Status — runtime state within the workflow.
- Parent card — optional; used for epic implementation children under a shared parent.
- Priority / tags / progress — optional organization helpers.
Analyst2
Invite-code join flow
📝
AnalystPRD ready for review...
dreeft AI versus BYOK onboarding copy
🔍
AnalystStatus lifecycle
Statuses you may see include:
| Status | Meaning |
|---|---|
| idle | Not currently in an active run |
| queued | Waiting for an available run or an earlier epic task |
| processing | Agent is actively working |
| wait_for_input | Agent posted a form or needs your answer |
| wait_for_review | Agent finished its stage and is waiting for a human decision |
| completed | Finished successfully |
| failed | Run ended in error or the linked PR closed without merge |
State diagram
tip
Use the card panel as the source of truth. Parent epic cards and standalone cards can behave slightly differently.
Moving cards
- Drag a card to another column to hand off to the next stage.
- After Analyst, the product can create the next handoff with Send to Architect.
- After Architect, Implement all creates child coder cards and task specs in dependency order.
- In Coder, epic children run under a shared parent card and shared PR flow.
Comments vs artifacts
- Comments — discussion, agent messages, and forms for structured Q&A.
- Artifacts — durable outputs such as PRDs, ADRs, task specs, and PR links.
In the current product, user comments belong to top-level cards. Child epic tasks still show system and agent updates, but discussion happens on the parent card.