iterel
/

Workflow

Backlog and task management

Organize work into epics, tasks, and priorities with the kanban board.

User-facing guide
Jump to first section

The kanban board

Open the Backlog from Planning, Backlog in the sidebar. Tasks are organized into columns:

  • To Do — work that needs to start
  • In Progress — actively being worked on
  • Done — completed work
  • Blocked — tasks that cannot proceed

Drag tasks between columns to update their status.

Epics

Epics group related tasks. Click Create epic to add one. Each epic can be expanded or collapsed and shows progress at a glance. Organize epics by category — for example, "Research Sprint," "Homepage Design," or "Authentication Flow."

Creating tasks

Use the Quick Add bar at the top of any column to create tasks inline. Type a title and press Enter.

Click any task to open the detail drawer where you can edit:

  • Title and description
  • Priority — P0 (critical), P1 (high), P2 (medium), P3 (low)
  • Type — generation, research, refactor, design, and more
  • Status — To Do, In Progress, Done, Blocked

The drawer also shows execution history and which section the task relates to.

Version history

The backlog tracks generation versions. When you regenerate tasks, previous versions are preserved. Click the version history panel to compare or revert.

Agent-suggested tasks

Tasks don't only come from you. As the project progresses, agents propose work they think should happen next — a Researcher might add "Interview 3 power users," the Designer might add "Resolve modal vs. drawer for settings," the Engineer might add "Add error boundary around the checkout flow." Agent-suggested cards appear with the agent's avatar on the stripe and a small chip noting why they were proposed.

You stay in control:

  • Approve — the card becomes a normal task you can drag through the columns.
  • Edit then approve — open the detail drawer, adjust the title, scope, or priority, then accept.
  • Dismiss — the card disappears and the agent will not propose the same thing again in this project.

Agents respect your Conductor autonomy level. On Guided, every suggestion waits for your approval. On Proactive, low-risk tasks (small refactors, lint fixes, doc updates) may slot themselves into To Do automatically. On Full Auto, agents add and execute tasks without asking.

Diff review for generated work

When an agent runs a task that produces code or design changes, you don't merge blindly. Open the task in the detail drawer and click Review changes to see every file the agent touched as side-by-side diffs. Step through hunks with Next/Previous, accept individual hunks, or reject the whole task. Nothing is committed to the project until you accept.

Integration with the workflow

Running a task can navigate you to the relevant section and trigger the appropriate agent. For example, a "Generate user personas" task opens Research and invokes the Researcher.

  • For directing work through conversation, read Conductor.
  • For controlling how much agents do on their own, read Autonomous mode.