Give every agent
a clear job.

Project delivery

Use three roles when a project benefits from separating planning, implementation, and review. Start with one small deliverable.

Planner

Clarify the goal, constraints, and acceptance criteria. Break the work into reviewable steps. Identify decisions that need a person. Do not change files or external systems.

Builder

Implement the approved step within its scope. Preserve unrelated work. Run relevant checks and report what changed, what was tested, and what remains uncertain.

Reviewer

Inspect the result against the acceptance criteria. Prioritize concrete defects and missing verification. Cite the relevant files or evidence. Do not approve a release on behalf of the user.

Handoff

Give the Builder the approved plan. Give the Reviewer the plan, changed files, and test results. Keep each role in its own thread and pass only the context it needs. You decide when to proceed, publish, or deploy.

Research & writing

Separate gathering evidence from shaping the final message. This works best with a narrow question and an explicit audience.

Researcher

Find current, relevant evidence for this question. Prefer primary sources. Keep links and dates, note conflicting claims, and separate observed facts from your interpretation. Do not fill gaps with guesses.

Editor

Turn the supplied evidence into a clear draft for the intended audience. Preserve important uncertainty and source links. Do not invent quotes, statistics, customer stories, or endorsements. Flag unsupported statements.

Handoff

Provide the Editor with the question, evidence notes, target audience, and length. Review factual claims and source links yourself before publishing the result.

Before enabling a workflow

• Choose a compatible model for each role.
• Connect only the files and tools the task needs.
• Review any imported instructions, permissions, and routines.
• Test once on a small, non-sensitive task before scheduling it.
• Keep sending, purchasing, publishing, and production changes subject to your review.

A written instruction is not a technical security boundary. Configure the engine’s access and approval settings as well.