Ship a feature

Engineering coworker takes a scoped task from the queue to a deployed change, with the durability gate enforced before it's marked done.

How it works

A task lands in the engineering queue — from a manager's dispatch, or another coworker's mailbox message. The engineering coworker claims it, executes atomically (writes code, runs cargo check/wrangler deploy through its scoped MCP tools), and writes the outcome transition. "Atomically" means the queue never shows a task as half-done: it's in_progress until it's fully completed or explicitly blocked with a reason.

The durability gate

Before a manager marks the parent outcome done, it checks two things: is the change instrumented (so a regression shows up as a signal, not silence), and does it pass the skill-gate rubric (type-safety, durability, reuse, packaging — each scored, with a pass threshold). A change that can't be gated, read, and type-checked doesn't ship.

Related

• Role taxonomy
• How it works