agent-creator

Sub-agent definitions require a structured blueprint with YAML frontmatter, standardized templates, and quality guidelines to ensure predictable, safe, and reusable agents. You can copy a starter template and adapt it using provided references.

Five design patterns exist for building autonomous agents: Domain Expert, Project-Specific, Utility, Orchestrator, and Autonomous. Each provides structured templates tailored to specific sub-agent use cases and integration needs.

Tool access modes for sub-agents include full, explicit, and inherited options. Usage guidelines help determine the appropriate mode for your agent, ensuring safe and predictable tool integration protocols.

The best way to ensure consistent sub-agent creation is to use starter templates and quality checklists. These provide proven, structured blueprints that meet standardized guidelines for predictable, reusable agents.

Yes, real-world examples drawn from existing agents and projects serve as references. These examples demonstrate practical application of design patterns, tool access modes, and integration protocols for new sub-agent definitions.

Use the Orchestrator pattern when your sub-agent coordinates multiple agents or tasks, and the Autonomous pattern when it operates independently. The blueprint provides guidelines for selecting the appropriate design pattern based on your integration requirements.