A CRUX workflow: statuses, roles and levels

A tracker board: Backlog has no flow, and every other column carries the role that owns it and the agents that help there; below, the task types Epic, Story, Task and Bug and a point scale.

CRUX team · · Updated · 6 min read

Your team already has a tracker: a board with columns, task types, maybe story points. A CRUX workflow replaces none of it. It is a short set of rules on top: which statuses CRUX acts on, who owns each one, which agents help there, which task types agents may create and what points they may set. This post goes through each part, shows where it lives in the dashboard and ends with four ways to set one up. (For why a workflow beats writing prompts by hand, see Stop writing prompts.)

Statuses and flows

A flow is one tracker status CRUX acts on. You don't have to cover the whole board: a column CRUX should leave alone simply has no flow. Each flow says three things:

  • Who owns the status: one role, such as Developer or QA.
  • Who helps there: chat agents, which people talk to in the task's chat while it sits in that status, and a pipeline: numbered steps, say plan, implement, review, each ending in an artifact posted to the task.
  • Which column it means: CRUX matches a flow to a column of your board by name. When the names differ, it proposes the closest column of the same kind (not started, in progress, done or cancelled), and you can pick one by hand.

Nothing starts by itself when a task moves. A person starts each chat and each pipeline step, and people check the result at the approval checkpoints where a wrong turn is still cheap to fix. One flow is the entry flow: the status where new work lands, for example a task created from a chat.

Two flow cards from the Overview: In Progress and In Review, both owned by the Developer role, each with no chat agents and a one-step pipeline (planner on In Progress, reviewer on In Review); In Progress's board column needs attention and In Review is not on the board.
Two flowsOne card per status: the role that owns it, its chat agents, its numbered pipeline and the board column it means.

Roles and I work as

A role is a hat a person wears on this project. A new workflow starts with the template's roles, each with a short description, a colour and an icon. Rename them, add your own, remove the ones you don't need; a workflow keeps at least one.

Every status has one role, and you set it: when you set up the workflow, or later in Statuses & flows. Only your team knows whether "In Review" belongs to a developer or to QA.

Roles decide what each person sees. On the project's Workspace page, the I work as switch has a segment for each role you hold, plus All my roles. Pick Developer and you see only the statuses Developer owns and the agents that help there, with a count of the sessions waiting for you. You choose your roles on the home page.

Levels: your tracker's own task types

A level is a task type your tracker already has: Epic, Story, Task, Bug, under the names your tracker uses. Each level carries two templates that agents follow when they create a task of that type: a description of what the level is for, and a structure for the task's text, such as Steps to reproduce, Expected, Actual for a bug.

CRUX never creates task types, statuses or fields in your tracker, and never asks you to. It works with the board you have:

  • A tracker with its own types (Jira; Plane with work item types on; GitHub with organization issue types): the levels are those types. To use another type as a level, create it in your tracker first.
  • A tracker without them (Linear; GitHub without issue types; Plane with types off): a level travels as an LV: label on the task, made the first time it is needed.

The Board fit panel shows how your tracker carries each level: as its own type, or by label.

Estimates

Estimates are optional. Switch them on and give agents a point scale, such as 1, 2, 3, 5, 8. Where your tracker has its own estimate (Jira's story points, a Linear team with estimates on), agents write it there. Anywhere else, CRUX writes an EST: label the first time a task gets that estimate. Switch estimates off, and agents set no points and write no labels.

The Levels & estimates page: four levels (Bug, Epic, Story, Task), estimates switched off, and Board fit showing Bug, Story and Task as the tracker's own types and Epic carried by a label.
Levels & estimatesThe levels and their templates, the estimates switch, and how your tracker carries each level.

Where each part lives

Everything above sits in the project's Workflow area, one section per part:

  • Overview: the whole workflow on one read-only board. A card per flow shows its status, role, chat agents, pipeline and board column; side cards sum up roles, levels, estimates, skills and more. Left to do lists what makes the setup fragile, each item with a link to where it is fixed.
  • Statuses & flows: add a flow, bind it to a column, pick its role and agents.
  • Roles: the role cards, and which statuses each role owns.
  • Agents: every chat and pipeline agent, with its prompt, model and tools.
  • Levels & estimates: the levels with their templates, the point scale and Board fit.

The rest of the sidebar holds the agents' toolkit (skills, MCP servers, the ADVISORS.md house rules for agents on CRUX), the retrospective, and Repository & versions: a workflow can live as files in .crux/ in your repository, so you can import it from a branch, export it as a pull request, and review a change before you activate it.

Four ways to set one up

While a project has no workflow, the Workflow area opens a short wizard instead of the Overview. It offers four ways to start:

  1. Talk it through with your AI agent (recommended). Connect your coding agent to CRUX and run /crux:crux-config in your checkout. The agent interviews you about your board and your team, then opens a pull request with the workflow. It waits as a pending version: merge the pull request and CRUX activates it (if review edits changed it, you confirm the new version in the dashboard), or activate it earlier in the dashboard.
  2. Start from the template. CRUX's generic workflow, matched to your board's statuses. You choose which statuses to keep, the role of each status and which agents stay.
  3. Build from my board. One flow per column of your board. Keep the columns CRUX should act on, pick the levels and the role of each status, and add agents later.
  4. Import from repo. If a branch already holds a workflow in .crux/ (exported from another project, say), preview it and import it as it is. This one needs a connected repository.

The template and board paths are a draft: nothing is saved until you press Create workflow. Afterwards, the Overview's Left to do list also reminds you to review the agents' prompts and add skills and MCP servers, beside any flow not yet bound to a column.

In short

  • A workflow is a few rules on top of your tracker. It changes nothing on your board.
  • A flow is one status CRUX acts on: its role, its chat agents, its pipeline and its column. A person starts every run.
  • You set the role of each status, and I work as shows each person their part.
  • Levels are your tracker's own task types, and CRUX never creates them. Estimates are an optional point scale.
  • Start by talking it through with your AI agent, from the template, from your board, or by importing from a repository.