agent-development

Create a Markdown file in the plugin's agents/ directory with YAML frontmatter containing name, description, model, and color fields, followed by a second-person system prompt. The description must include triggering conditions and 2-4 example blocks showing when the agent activates.

Agents require name, description, model, and color fields, with tools being optional. The name must be 3-50 lowercase characters with hyphens, and the description must contain triggering conditions plus example blocks.

Start with "Use this agent when" followed by specific conditions, then add 2-4 example blocks containing context, user request, assistant response, and commentary explaining why the agent triggers. Cover different phrasings of the same intent.

Use inherit so the agent runs on the same model as the parent conversation, which is the recommended default. Choose sonnet, opus, or haiku only when the agent has specific capability, speed, or cost requirements.

Add a tools array to the frontmatter listing only the tool names the agent needs, such as ["Read", "Grep"] for read-only analysis. Omitting the field grants access to all tools, so apply least privilege.

Agent identifiers must be 3-50 characters using only lowercase letters, numbers, and hyphens, and must start and end with an alphanumeric character. Underscores, spaces, leading or trailing hyphens, and names under 3 characters are invalid.