Skip to main content

​
Multi-agent development

You can run a multi-agent board by giving each agent a narrow role and letting Pulse enforce the boundaries. A simple production setup is Spec + Executor + Validator.

​
Team structure

Add QA when test scenario ownership should be separate from implementation.

​
Setup

Create the agents in the web UI, assign presets, then export MCP config.

​
Workflow

  1. Spec agent creates ideation and asks ambiguity-killer questions.
  2. Spec agent derives or writes the spec.
  3. Validator submits spec validation when evidence is ready.
  4. Spec agent derives cards and a sprint.
  5. Executor implements cards and moves them to validation with conclusions.
  6. Validator submits task validation and routes each card.

​
Preventing cross-role drift

The important rule is that implementers do not validate themselves. Executor can read validation records but cannot submit them or move validation -> done.

​
Board-level overrides

Use board overrides to restrict an agent on a sensitive board. For example, keep a shared Reporter read-only on production boards while allowing broader reads on evaluation boards.

​
Common failure modes

Last modified on May 8, 2026