Overview Shipped
Every stage opened up on its own: what it receives, what it decides, where it can fail, and which of its guarantees are held by a test rather than a promise.
Each stage below is a real boundary in the engine, with its own inputs and its own tests. They are listed in execution order, and each one narrows or enriches what the next one receives.
In order
- ChangesetWhat changed, and what technologies it touches.
- Choosing the rosterScope, signals, and an interest poll.
- Pre-checksWhat your own linters and typecheckers already know.
- ReviewA worker-then-verifier pillar per specialist, concurrently.
- MergeWhich findings are the same defect, and what is already known.
- ScoringWhat each finding is actually worth.
- Gate & reportReady or not, and the write-up you read.
Step 4 is drawn as one step and is not one: each specialist is its own worker-then-verifier pillar and the pillars run concurrently, so there is no point at which the whole roster waits on the slowest lane.
Run it
myteams devteam review code --base main
myteams devteam review code 3:3 --security --data
myteams devteam review code --effort high --fix recommended