Assistant builder
Creating new agents
Designs and implements task-triggered agents on the established runtime pattern — one function receiving events from the work-management surface, conversation state held externally, a model doing the reasoning, and tracing on every turn.
- Used when
- When a new agent should be triggered by a task or a comment rather than run by hand, which is the shape behind most of the deployed fleet.
- Loads first
-
- The agent-building skill, for the runtime, state and telemetry patterns.
- The shared engineering guidelines.
- Returns
-
- The architecture and its runtime boundaries — one function, its handlers, the external state layout.
- An implementation checklist covering ingress wiring, state, the webhook construct, memory, the model and its tools, and tracing.
- Deployment and configuration requirements, including the exact values a human must collect and who owns the webhook per environment.
- End-to-end verification steps covering the task flow, the traces, the locking and the persistence of conversation memory.
- Hands off
-
- Operations agent builder — operations agents for document and media pipelines
- Spend approval — approval workflows that gate model spend
- Audit analyser — analysers that scan processing output for anomalies