549a0646d7
- .claude/agents/test-runner.md: New Claude Code agent definition for running cargo test suites and analyzing results, configured with haiku model for fast execution. - skills/agent-swarm-launcher/: New skill for bootstrapping coordinated multi-agent workflows with AGENTS.md reconnaissance, Agent Mail coordination, and beads task tracking. - api-review.html, phase-a-review.html: Self-contained HTML review artifacts for API audit and Phase A search pipeline review. - .beads/issues.jsonl, .beads/last-touched: Updated issue tracker state reflecting current project work items. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
name, description
| name | description |
|---|---|
| agent-swarm-launcher | Launch a multi-agent “swarm” workflow for a repository: read and follow AGENTS.md/README.md, perform an architecture/codebase reconnaissance, then coordinate work via Agent Mail / beads-style task tracking when those tools are available. Use when you want to quickly bootstrap a coordinated agent workflow, avoid communication deadlocks, and start making progress on prioritized tasks. |
Agent Swarm Launcher
Workflow (do in order)
-
Read all
AGENTS.mdandREADME.mdfiles carefully and completely.- If multiple
AGENTS.mdfiles exist, treat deeper ones as higher priority within their directory scope. - Note any required workflows (e.g., TDD), tooling conventions, and “robot mode” flags.
- If multiple
-
Enter “code investigation” mode and understand the project.
- Identify entrypoints, key packages/modules, and how data flows.
- Note build/test commands and any local dev constraints.
- Summarize the technical architecture and purpose of the project.
-
Register with Agent Mail and coordinate, if available.
- If “MCP Agent Mail” exists in this environment, register and introduce yourself to the other agents.
- Check Agent Mail and promptly respond to any messages.
- If “beads” tracking is used by the repo/team, open/continue the current bead(s) and mark progress as you go.
- If Agent Mail/beads are not available, state that plainly and proceed with a lightweight local substitute (a short task checklist in the thread).
-
Start work (do not get stuck waiting).
- Acknowledge incoming requests promptly.
- Do not get stuck in “communication purgatory” where nothing is getting done.
- If you are blocked on prioritization, look for a prioritization tool mentioned in
AGENTS.md(for example “bv”) and use it; otherwise propose the next best task(s) and proceed. - If
AGENTS.mdreferences a task system (e.g., beads), pick the next task you can complete usefully and start.
Execution rules
- Follow repository instructions over this skill if they conflict.
- Prefer action + short status updates over prolonged coordination.
- If a referenced tool does not exist, do not hallucinate it—fall back and keep moving.
- Do not claim you registered with or heard from other agents unless you actually did via the available tooling.