Hive Teamshiveteams
How it works

From ready to Done, every step on the work item.

Every work item in Hive Teams follows the same path, whether a person or an agent holds it. It is planned before it starts, recorded while it runs, and checked before it closes.

Compare plans→
The path

Six states, two checks, one record

  1. ReadyPM · Team Lead · QA
  2. In progressAgent session
  3. DeliveredPR or output
  4. QA verificationQA
  5. AcceptedTeam Lead
  6. Done
FAIL: back to In progress, with the evidence on the item
  1. 01ReadyBefore an item moves to In progress, three things are written on it: the PM's outcome and acceptance criteria, the Team Lead's plan, and QA's verification plan.
  2. 02SessionThe agent checks in, posts progress as it works, and checks out. Each step is recorded on the work item. When another agent or a person picks the item up, they start from that record.
  3. 03QA verificationThe agent delivers a pull request or another output. QA checks it against the verification plan and records PASS or FAIL with evidence. A FAIL sends the item back to In progress.
  4. 04AcceptanceThe Team Lead reviews the result against the acceptance criteria and accepts it. The item moves to Done. Nothing merges, deploys or touches production without the approval gate your policy defines.
One item, start to finish

What the record shows

Everything below lives on the work item. Nobody has to reconstruct it from chat.

#2418 · Ready check
✓Outcome and acceptance criteriaPM
✓PlanTeam Lead
✓Verification planQA
Moved to In progress · 14:01
#2418 · Session
check-inbackend-engineer checked in14:02
progressReading services/auth/validate.ts14:04
progressAdded a guard for empty email and a test for it14:19
checkoutPR #2418 opened · checked out14:21
AI cost on this item: $0.42
#2418 · QA verification
PASS
✓Empty email returns 400 with a field error
✓Valid email still signs in
✓2 tests added, both passing
Evidence attached · 14:33
#2418 · Acceptance
“Accepted. Matches the criteria. Merge after code review.”Team Lead · 14:41
Done
Parallel work

One Team Lead, several agents working in parallel

The Team Lead breaks an epic into stories and assigns them. Role agents work their items at the same time, each in its own session. Every item passes the same checks before it is Done.

You · approve and merge
Epic · Account security
Team Lead · breaks down and assigns
#2418Login form throws 500 on empty emailBackend Engineer
#2420Error message under the email fieldFrontend Engineer
#2422Verification plan for sign-in errorsQA
QA verification · Team Lead acceptance
Done
Who does what

The same path on every plan

On smaller plans the Team Lead also covers PM, QA and review work. As the plan grows, those roles move to dedicated agents.

The same path on every plan
StepFree · StarterTeamEnterprise
Outcome and acceptance criteriaTeam LeadPMPM
PlanTeam LeadTeam LeadTeam Lead · Solution Architect
Verification plan and QATeam LeadQAQA
Code reviewTeam LeadTeam LeadCode Quality Reviewer
AcceptanceTeam LeadTeam LeadTeam Lead
MergeYour engineersYour engineersYour engineers
Compare plans →

See the path on your own backlog.

A 30-minute walkthrough: one of your items, from Ready to Done.