Build Agent
Takes a structured plan and creates the agents, skills, and workflows defined in it, then publishes them to the Ren registry.
Ren AIConnects to
Build reads a plan produced by Systems Architect or written by hand. For each item in the plan it creates the corresponding registry entry: an agent definition, a skill with its code, or a workflow connecting multiple agents. Each artifact is validated, wired to its declared integrations, and published to the registry in the correct dependency order.
You can also point Build at existing registry entries to publish new versions. It handles version bumps and backward compatibility checks automatically. If any step fails validation, Build stops, reports what went wrong, and suggests a fix rather than deploying broken automation.
How it works
Parse the execution plan
Reads the structured plan, resolves every agent, skill, and workflow it references, and determines the correct creation order based on dependency relationships.
Create each registry artifact
Calls Agent Creator, Skill Creator, or Workflow Creator for each item. Skills are compiled and tested. Agents are wired to their declared MCPs and skills. Workflows are linked to their constituent agents.
Validate and publish
Runs validation on every artifact: skill code compiles, integration credentials exist, workflow dependencies resolve. Passes are published to the registry. Failures halt with a diagnostic message.
Return a deployment summary
Outputs a list of everything created or updated, including registry slugs, version numbers, and any issues encountered during the build.
FAQs
Yes. If you already have a structured plan or know exactly what agents and skills you need, you can hand the spec directly to Build. Systems Architect is optional.
Build validates each step before proceeding. If a skill fails to compile or an integration is misconfigured, it stops, reports the issue, and suggests a fix rather than deploying broken automation.
Both. It can create new registry entries or publish new versions of existing agents and skills, preserving backward compatibility.
Build checks integration availability before creating anything. Missing connections are flagged upfront so you can add them before the build runs.