Starter agentspace repository that follows the current AgentSpec layout used by Orchestrator.
agentspec/with starter specs for workspace, environments, agents, skills, tools, and automationsprompts/with role prompts (orchestrator,executor)tools/for custom tool implementationsreference/agentspec.mdwith the full AgentSpec referencereference/agentspec-bundles.mdwith canonical bundle shapes
- Review
agentspec/workspace.yamlfor workspace-level defaults (autonomy mode, tool policy). - Set required secret keys in
agentspec/environments/default.yamlto match your workspace secrets. - Adjust agent defaults in
agentspec/agents/*.yaml(harness, model, prompt paths). - Define tool contracts in
agentspec/tools/*.yaml(builtin/local/connector) and align them with runtime tools. - For local tools, set
spec.modulePathto an existingtools/*.tool.ts|js|mjsmodule. - Update
agentspec/automations/triage-issues.yamlwith the right labels,environmentKey, and optionaltarget.repo. - Remove or edit starter tool and automation examples before production use.
- Commit and push. Reconcile applies this desired state in your workspace.
- Keep
apiVersionasagentspec.orchestrator.dev/v2alpha1. agentspec/workspace.yamlis required and must usemetadata.key: workspace.- Keep
metadata.keystable after creation. Renames should be delete + create. - Exactly one default environment should be marked with
spec.isDefault: true. - Exactly one default agent definition per role should be marked with
spec.isDefault: true. - Prompt paths in agent specs must exist in
prompts/. - Repositories are not declared in agentspec. Connect them through GitHub, then target them from automations with
spec.target.repowhen needed.
- Workspace key:
workspace - Environment key:
default - Agent keys:
orchestrator,executor - Tool keys:
builtins,find-bugs - Automation key:
triage-issues - Skill key:
code-review
If you change keys, update all references across files.