Feature: Agent Tags for cross-division discovery

[kienbui1995]

Problem

Agents are organized by division, but many tasks span multiple divisions. A user looking for help with API security might need:

• Security Engineer (engineering)
• API Tester (testing)
• Backend Architect (engineering)

There is no way to discover agents by capability across divisions.

Proposal

Add an optional tags field to agent frontmatter:

---
name: Security Engineer
description: Threat modeling, secure code review, security architecture
tags: security, code-review, ci-cd, api, compliance
color: red
---

Benefits

• Cross-division search: ./scripts/search.sh --tag security finds agents across engineering, testing, specialized
• Better tool integration: tools like MCP servers, search CLI, and web dashboards can use tags for smarter matching
• Contributor guidance: tags make it clear what capabilities exist and where gaps are
• Backward compatible: tags field is optional, existing agents work without it

Tag conventions

• Lowercase, hyphenated (e.g., code-review, api-design)
• Max 5-7 tags per agent
• Community-driven taxonomy (no strict ontology needed)

Rollout

1. Add tags as optional field in frontmatter spec
2. Update lint-agents.sh to validate tag format (if present)
3. Add tags to a few agents as examples
4. Community adds tags via PRs over time

Open questions

• Should tags be freeform or from a controlled vocabulary?
• Should convert.sh include tags in generated files for tools that support metadata?

Happy to start with a small PR adding the spec and tagging a few agents as proof of concept.