Agent Starter Templates
Starter Templates are pre-built, production-ready agent blueprints designed to accelerate common workflows. Each template includes pre-written system instructions, recommended tools, skills, and sub-agents. Unlike built-in agents, templates are fully editable — use them as starting points and customize every field to fit your needs.
Available Templates
Orchestra ships four starter templates covering key automation scenarios:
Lead Product Manager guiding ideation, codebase exploration, and ticket creation. Recommended for product strategy and feature scoping.
- Ideation and brainstorming
- Codebase exploration
- Jira ticket creation
Technical architect for implementation planning. Analyzes codebase, proposes architecture, and generates development roadmaps.
- Architecture analysis
- Technical planning
- Implementation roadmaps
Playwright-powered automated UI testing agent. Validates user workflows, generates test cases, and documents test coverage with screenshots.
- Playwright test generation
- UI validation
- Test documentation with images
Senior Business Analyst & Product Manager. Conducts multi-round discovery, generates Functional Requirements, and creates Jira epics.
- Requirements discovery
- Epic creation
- User story generation
Using Templates
Starter Templates are accessed from a dedicated Templates page in the workspace sidebar.
Click Templates in the sidebar under your workspace to view the template catalogue.
Click the 💡 icon to preview template details (tools, skills, sub-agents, workflow examples), or click Use Template to proceed to agent creation.
All template fields are fully editable. Modify name, role, instructions, tool selections, or any other field. Submit to create your custom agent.
Fully customizable: Templates are starting points, not locked blueprints. Every field — name, role, capabilities, instructions, tools, skills — can be edited before creating the agent. There are no field restrictions or versioning requirements.
Predefined Tools
Each template includes a recommended set of tools, pre-selected and ready for use. When you use a template, these tools are automatically added to the agent form. You can:
- Add or remove tools freely
- Modify tool selections before deployment
- Use the template's suggestions as a starting point
Tool Categories & Filtering
Some templates use tools from specific categories (e.g., INTERNAL tools). The template registry handles category-aware tool matching:
- Category specified: Only tools matching both the action name and category are selected
- Category omitted: Tools are matched by action name only, regardless of category
Example: The QA Agent template specifies the INTERNAL category for add_comment and add_comment_with_images tools. This prevents Jira tools with the same action names from being selected — only INTERNAL tools matching those names are pre-selected.
Regular vs CLI Templates
Starter Templates come in two flavors, each suited to different use cases:
| Aspect | Regular Templates | CLI Templates |
|---|---|---|
| AI Provider | Uses workspace default model | Requires CLI integration (GitHub Copilot, etc.) |
| Navigation | Routes to /agents/new | Routes to /agents/new-cli |
| Setup | Faster — minimal configuration | Requires CLI integration selection + reasoning effort |
| Use Cases | Product planning, analysis, discovery | Code generation, testing, file operations |
| Examples | Product Brainstormer, Dev Planning Agent, BA Agent | QA Agent |
Template Workflow
↓
Use Template
↓
/agents/new (pre-populated)
↓
Customize & submit
↓
Agent created with workspace AI model
↓
Use Template
↓
/agents/new-cli (pre-populated)
↓
Select CLI integration & reasoning
↓
Customize & submit
↓
Agent created with CLI provider
Best practice: Review the template's usage information (via the 💡 Details button) to understand recommended tools, sub-agents, and common workflows before deploying. This ensures you don't miss optional but valuable integrations.