Skip to content
Agent Workflows

/work

Execute one selected plan and continue autonomously through review preparation.

/work requires an agent-planned item and executes its approved plan autonomously, one todo at a time. Standalone work automatically resumes when the item contains a delivery backlink, keeping the referenced local plan and its todo states. It resolves the exact linked open request and safely switches to its existing source branch before changing any file. A missing local branch or unsafe checkout stops delivery. After checkout, the item moves to in progress while work and inspection run. Otherwise, it copies the published plan locally and initializes delivery. It routes each todo to the right specialist and hands the completed plan directly to /ready without another approval.

How /work executes a plan

01 · New work onlyInitialize deliveryMove the item to in progress and create a branch with a linked draft request.
Todo execution loop
02 · AutonomousImplement one todoSelect the right specialist and route only the skills its activity triggers.
03 · AutonomousValidate and commitCommit and push the result, persist completion, and continue with the plan.
Next todo
Workflow/readyCheck the complete branch and prepare the request for inspection.
Corrective loopReadiness gaps or blocking inspection findings return to /work as new todos.

Skills used under the hood

/work selects the most suitable specialist for the active todo. That specialist loads only the skills whose triggers apply and may work directly when none are needed.

Browse the routed skills

What /work does

1Initialize or resumeFor new work, move the item to in progress and create a work branch with a linked draft request. For resumed work, check out the existing request branch safely and move the item to in progress.
2RouteSelect or reuse the most suitable specialist for the active todo and load only the skills its activity triggers.
3ExecutePersist the todo as in progress, implement and validate only its scope, then stage only its changes.
4CommitCommit the result, persist todo completion immediately, push the commit, and continue. A todo without a commit causes no push.
5ReadyWhen every todo is complete, continue automatically to /ready; later findings return through the same loop as corrective todos.