Private betaPlane integration liveJira planned
CRUX is an agile delivery process for teams of people and AI agents, on top of the tracker you already use — Plane today, Jira planned. Each status belongs to a role. Its agents ask, then draft; every step ends in a versioned artifact on the ticket that waits for your ok.
Which seat is yours?
Not sure? Every ticket starts with the Boss — the domain expert.
01Your seatBoss
The domain expert. Every idea enters through the Boss and is clarified in business language before anyone designs or builds.
Your statuses in the workflow editor
02Boss
What reaches you, what you approve, and who reads it next. Demo ticket CHK-12 · Apple Pay in checkout.
Reaches you
Customers keep asking to pay with Apple Pay. Can checkout support it? The receipt email should say how they paid.
You approveCHK-12 · Apple Pay in checkout
### 📦 ARTIFACT: domain-qa v1 - agent: domain-interviewer · skill: domain-interview - consumes: ticket description - approved-by: — waiting — ---
domain-qa v1 waits for your ok.Silence is not approval.
Goes on to
domain-qa →
03Boss
The human moves the ticket
When its step is finished, the agent stops. Moving the ticket to the next status is your decision — at every status, all the way to Done.
from the agent prompts
**You move nothing.** Do not call `ticket_set_status` — the human routes the ticket onward.Your part, in this seat
01Your seatDesigner
Turns what the client wants to see into a structured design brief, every screen state included.
You approveCHK-12 · Apple Pay in checkout
### 📦 ARTIFACT: design-prompt v1 - agent: designer · skill: design-brief - consumes: domain-qa, ticket description - approved-by: — waiting — ---
design-prompt v1 waits for your ok.Silence is not approval.
02Designer
What reaches you, what you approve, and who reads it next. Demo ticket CHK-12 · Apple Pay in checkout.
Reaches you
Customers keep asking to pay with Apple Pay. Can checkout support it? The receipt email should say how they paid.
On your desk above
design-prompt v1draft · waits for your ok
design-prompt sits beside your role flow, waiting for you.
Go to itGoes on to
design-prompt →
03Designer
The human moves the ticket
When its step is finished, the agent stops. Moving the ticket to the next status is your decision — at every status, all the way to Done.
from the agent prompts
**You move nothing.** Do not call `ticket_set_status` — the human routes the ticket onward.Your part, in this seat
01Your seatQA
Plans the tests before the code: numbered requirements, atomic checks, test cases. Turns raw bug reports into Bug tickets.
02QA
What reaches you, what you approve, and who reads it next. Demo ticket CHK-12 · Apple Pay in checkout.
Reaches you
Customers keep asking to pay with Apple Pay. Can checkout support it? The receipt email should say how they paid.
You approveCHK-12 · Apple Pay in checkout
### 📦 ARTIFACT: requirements v1 - agent: qa-requirements · skill: requirements-review - consumes: ticket description, domain-qa, design-prompt - approved-by: — waiting — ---
requirements v1 waits for your ok.Silence is not approval.
Goes on to
requirements →
03QA
The human moves the ticket
When its step is finished, the agent stops. Moving the ticket to the next status is your decision — at every status, all the way to Done.
from the agent prompts
**You move nothing.** Do not call `ticket_set_status` — the human routes the ticket onward.Your part, in this seat
01Your seatProject manager
Splits a clarified request into Agile tickets, estimates them, plans two-week cycles and drafts client status reports.
You approveCHK-12 · Apple Pay in checkout
### 📦 ARTIFACT: decomposition-plan v1 - agent: project-manager · skill: decompose - consumes: requirements, domain-qa, tech-qa, design-prompt, ticket description - approved-by: — waiting — ---
decomposition-plan v1 waits for your ok.Silence is not approval.
02Project manager
What reaches you, what you approve, and who reads it next. Demo ticket CHK-12 · Apple Pay in checkout.
Reaches you
On your desk above
decomposition-plan v1draft · waits for your ok
decomposition-plan sits beside your role flow, waiting for you.
Go to itGoes on to
decomposition-plan →
Children created in Backlog, each carrying its R# subset verbatim.
03Project manager
The human moves the ticket
When its step is finished, the agent stops. Moving the ticket to the next status is your decision — at every status, all the way to Done.
from the agent prompts
**You move nothing.** Do not call `ticket_set_status` — the human routes the ticket onward.Your part, in this seat
01Your seatDeveloper
Clarifies how it will be built, then runs the build steps in Claude Code on their own machine: code, review, wiki update and a verification pass against QA's test cases. Agents on the server read code and the wiki and write neither.
Your statuses in the workflow editor
02Developer
What reaches you, what you approve, and who reads it next. Demo ticket CHK-12 · Apple Pay in checkout.
Reaches you
You approveCHK-12 · Apple Pay in checkout
### 📦 ARTIFACT: tech-qa v1 - agent: developer-interviewer · skill: tech-interview - consumes: requirements, domain-qa, design-prompt, ticket description - approved-by: — waiting — ---
tech-qa v1 waits for your ok.Silence is not approval.
Goes on to
tech-qa →
03Developer
The human moves the ticket
When its step is finished, the agent stops. Moving the ticket to the next status is your decision — at every status, all the way to Done.
from the agent prompts
**You move nothing.** Do not call `ticket_set_status` — the human routes the ticket onward.Your part, in this seat
04Whole team
Roles, the agent catalog and the status rail are configured per project in the dashboard. Pick a status to see whose seat it is.
Statuses
They come from your tracker — create and reorder them there. This page uses Jira-style names.
Role flows
For every status: the role that owns it, its chat agents and the order of its pipeline.
Agent catalog
Provider and model, prompt, skills, and read access to code and wiki — set per agent.
Export and import
Carry a whole workflow from one project to the next.
Ten statuses, Backlog to Done
Rules every seat can count on
Every artifact is versioned
An artifact is what an agent hands you: a document posted on the ticket as a comment. Its header names the type and the version. A revision never edits the old comment — it is posted as a new v(N+1).
### 📦 ARTIFACT: domain-qa v1Approved by a human, in chat
The agent drafts in chat and posts only after an explicit ok.
"ок" / "approved" / "go ahead" — silence is not approvalThe original request is never edited
The ticket description stays the requester's words, verbatim. Agents only append artifact comments.
**Never edit the original ticket description.** It is immutable provenance.TrackerPlane · liveJira · planned, no date.
05Access
Seat you were looking atBoss
beta-request · Incoming_Request · to the CRUX team --- email: — name: — company: — team_size: — tracker: — lang: en ---