mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F 63b6114364 docs(lifecycle): add awaiting_pr_review to the task-states reference

The canonical task-states doc enumerated every waiting state EXCEPT awaiting_pr_review, and its transition table + flow diagrams omitted the in-path PR gate. Adds the state, a PR Review Gate flow (submit_up / submit_root -> awaiting_pr_review -> pr_pass / pr_fail), and the role-restricted transition rows (PM opens, pr_reviewer passes or fails).

2026-06-22 14:03:44 +02:00

3.3 KiB

Raw Blame History

Task States Reference

State Categories

Active States (Work happening)

claimed - Agent has ownership, about to start
in_progress - Active work
verifying - Self-verification
needs_revision - Fixing QA issues

Waiting States (On hold)

blocked - Waiting on dependency
paused - Temporarily stopped
awaiting_qa - Ready for QA review
awaiting_documentation - Ready for docs
awaiting_pr_review - Assembled cell→root / root→master PR awaiting the in-path review gate
awaiting_pm_review - Ready for PM approval
awaiting_ceo_approval - Major task, CEO review

Terminal States (Done)

completed - Work finished
cancelled - Work cancelled

Setup State

backlog - PM setup phase, not ready for work

State Transitions

Developer Flow

pending → claimed → in_progress → verifying → awaiting_qa
     ↑        ↓           ↑                         ↓
     └─ unclaim           └── needs_revision ←──────┘

QA Flow

awaiting_qa → claimed (claim_review) → pass/fail
                                          ↓
                         pass: awaiting_documentation
                         fail: needs_revision

Documenter Flow

awaiting_documentation → claimed (claim_doc_task) → awaiting_pm_review

PR Review Gate (assembled PRs)

in_progress → awaiting_pr_review (cell PM submit_up / Main PM submit_root opens the PR)
                   ↓
        pr_pass: awaiting_pm_review   (PR reviewer)
        pr_fail: needs_revision       (PR reviewer)

The cell PM's submit_up opens the cell→root PR and the Main PM's submit_root opens the root→master PR; both enter awaiting_pr_review for the in-path reviewer. Leaf developer tasks and branchless coordination roots skip the gate.

PM Activation

backlog → pending (a PM activates the task during `triage`)

Role-Restricted Transitions

Transition	Allowed Roles
`backlog → pending`	cell_pm, main_pm
`claimed → pending` (unclaim)	assignee or PM
`awaiting_qa → awaiting_documentation`	qa only
`awaiting_qa → needs_revision`	qa only
`awaiting_documentation → awaiting_pm_review`	documenter, developer (parallel)
`in_progress → awaiting_pr_review` (submit_up / submit_root)	cell_pm, main_pm
`awaiting_pr_review → awaiting_pm_review` (pr_pass)	pr_reviewer only
`awaiting_pr_review → needs_revision` (pr_fail)	pr_reviewer only
`awaiting_pm_review → completed`	cell_pm, main_pm
`awaiting_pm_review → awaiting_ceo_approval`	cell_pm, main_pm (parent tasks only)
`awaiting_ceo_approval → completed`	ceo only
`awaiting_ceo_approval → needs_revision`	ceo only
`any → cancelled`	cell_pm, main_pm, ceo

CEO Approval Notes

Only parent tasks (no parent_task_id) can be escalated to CEO
Subtasks are completed by their Cell PM, not the CEO
The CEO reviews the complete feature via the parent task

Checking State

You don't poll task state directly — every flow verb returns a standardized envelope whose status and next fields tell you the task's current state and what to call next. Trust the envelope rather than guessing. To pull the full task context (criteria, prior notes, handoff), call evidence(task_id).

3.3 KiB Raw Blame History