invoke_agent. It is not a Veryfront Code workflow primitive.
Agent-facing flow
- Load the Veryfront router skill:
load_skill({ "skillId": "veryfront" }). - Load this page as the canonical docs resource for the task.
- If the request is broad, ask exactly one short
form_inputwith one requiredbrieffield, then continue from the submitted brief. - Inspect existing agents plus relevant project tools and integrations before creating new primitives.
- Create or update the specialized project agents first. Keep the set minimal; for a broad starter, two specialists is a good default unless the brief clearly needs a different shape.
- Create or update one orchestrator project agent. Its instructions must explicitly call
invoke_agent, identify the specialist agent ids it delegates to, pass acontextobject for each delegation, and describe how it validates and combines specialist results. - Use live catalog and project tools to create or update the minimal required agents. Reuse existing agents when the brief asks to extend an existing setup.
- Summarize the orchestrator, specialists, delegation flow, assumptions, and verification steps. Include a chat action that tests the orchestrator agent.
Guardrails
- Do not load a removed
create-agentic-workflowsub-skill. - Do not invent integration IDs, tool IDs, provider tool IDs, schedule syntax, or resource IDs.
- Do not create a Veryfront workflow primitive for this starter.
- Do not call
create_workfloworupdate_workflow, and do not create aworkflows/file unless the user explicitly asks for the lower-level workflow API. - Do not use placeholder specialist agent ids such as
replace-me,todo, orplaceholder. - Do not create unrelated app, page, route, or chat UI files.
- Do not stop after only one helper agent or standalone files; the starter is complete when the orchestrator and needed specialist agents are created or updated.
- Prefer updating existing project primitives when the brief asks to extend an existing agent setup.
- When retrying after a partial run, re-use the submitted brief when available and repair existing incomplete agents instead of asking for the same brief again.
Example pattern
A common starter shape is one orchestrator plus two specialists:system maps to system_prompt in the MCP tool input. Resolve the actual specialist agent IDs before creating or updating the orchestrator instructions.
The orchestrator instructions should name the specialist agent ids, describe when each one is invoked, require
context on every delegation, and explain how conflicting or incomplete specialist results are handled.
Output shape
Return a short implementation summary with the orchestrator agent name and id, source path when available, specialist agent names and ids, tools or integrations used,invoke_agent delegation flow, assumptions, and how to test it in chat.