feat: add competitive swarm pattern and adding-swarm-patterns skill

[khaliqgant]

Summary

• Add competitive swarm pattern for multiple independent implementations followed by comparison and selection
• Create adding-swarm-patterns skill with guidance on adding new swarm techniques

Competitive Pattern

Multiple agent teams independently implement solutions to the same problem, then a lead compares outputs and selects the best approach. Useful for:

• Exploratory problems where multiple valid solutions exist
• High-stakes architecture decisions
• Innovation challenges
• Spike work to evaluate different technologies

Changes

• Add "competitive" to SwarmPattern type union
• Add "competitive" to JSON schema enum
• Create competitive.yaml template with 3 competing teams
• Add pattern documentation (docs/workflows/patterns/competitive.md)
• Add template documentation (docs/workflows/templates/competitive.md)
• Update docs/workflows/README.md with new pattern/template
• Create adding-swarm-patterns skill for future pattern additions

Test plan

• Verify TypeScript types compile
• Verify JSON schema validates
• Verify docs links work

🤖 Generated with Claude Code

---

[devin-ai-integration]

Devin Review found 1 potential issue.

🐛 1 issue in files not directly in the diff

🐛 "competitive" template missing from BUILT_IN_TEMPLATE_NAMES array (packages/broker-sdk/src/workflows/templates.ts:9-16)

The competitive template YAML file was added to builtin-templates/ but BUILT_IN_TEMPLATE_NAMES in packages/broker-sdk/src/workflows/templates.ts:9-16 was not updated to include "competitive". This means listBuiltInTemplates() and listTemplates() will not return "competitive" in their results.

Root Cause and Impact

The BUILT_IN_TEMPLATE_NAMES constant at packages/broker-sdk/src/workflows/templates.ts:9-16 is the source of truth for which templates are discoverable:

export const BUILT_IN_TEMPLATE_NAMES = [
  'feature-dev',
  'bug-fix',
  'code-review',
  'security-audit',
  'refactor',
  'documentation',
] as const;

This array is used by listBuiltInTemplates() (line 63-65) and listTemplates() (line 75-79). Without "competitive" in this array, users calling registry.listTemplates() — as shown in the docs at docs/workflows/README.md:55 — will not see the competitive template listed. The template can still be loaded directly via loadTemplate("competitive") since that uses file system resolution, but it is invisible to discovery APIs.

Impact: The competitive template is undiscoverable through the listBuiltInTemplates() and listTemplates() APIs, breaking the expected user workflow of listing available templates before loading one.

View 4 additional findings in Devin Review.