swarm
Tum ekibi ayni anda devreye sok. Agent'lar paralel calisir, birbirine soru sorar, birlikte gelistirir. Kullanim: /swarm <gorev>
Best use case
swarm is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Tum ekibi ayni anda devreye sok. Agent'lar paralel calisir, birbirine soru sorar, birlikte gelistirir. Kullanim: /swarm <gorev>
Teams using swarm should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/swarm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How swarm Compares
| Feature / Agent | swarm | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Tum ekibi ayni anda devreye sok. Agent'lar paralel calisir, birbirine soru sorar, birlikte gelistirir. Kullanim: /swarm <gorev>
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /swarm - Collaborative Swarm Mode Tum ana ekibi ayni anda devreye sokar. Agent'lar paralel calisir, shared dosyalar uzerinden haberlesir. ## Kullanim ``` /swarm Kullanici authentication sistemi ekle /swarm Bu projeyi bastan incele ve iyilestir /swarm Yeni e-commerce modulu gelistir ``` ## Adim 1: Proje Tespiti Once mevcut dizini tara: - Tech stack ne? - CLAUDE.md var mi? - Mevcut kod ne durumda? Yoksa `/project-detect` calistir. ## Adim 2: Shared Klasor Hazirla ```bash mkdir -p .claude/shared touch .claude/shared/swarm-questions.md touch .claude/shared/swarm-answers.md touch .claude/shared/swarm-review.md ``` Her dosyanin basina header ekle: ```markdown # Swarm Communication Log Gorev: <gorev aciklamasi> Baslangic: <tarih> ``` ## Adim 3: Phase 1 - Paralel Kesif 3 agent'i PARALEL calistir (Task tool ile): ### Agent 1: scout ``` Gorevi: Codebase'i tara, mevcut pattern'leri bul, dosya yapisini cikar. Cikti: .claude/shared/swarm-phase1-scout.md ``` ### Agent 2: project-manager (Sofia) ``` Gorevi: Gorevi alt gorevlere parcala, oncelik sir, bagimlilik belirle. Sprint backlog olustur. Cikti: .claude/shared/swarm-phase1-pm.md ``` ### Agent 3: architect ``` Gorevi: Mimari plan ciz, tech decisions yap, ADR yaz. Cikti: .claude/shared/swarm-phase1-architect.md ``` Phase 1 tamamlaninca: 3 ciktiyi oku, sentezle, Phase 2'ye gec. ## Adim 4: Phase 2 - Paralel Gelistirme Phase 1 ciktilarini her agent'a ver, PARALEL calistir: ### Agent 4: backend-dev (Dmitri) ``` Gorevi: API endpoints, database schema, business logic implement et. Input: Phase 1 sentezi + PM sprint backlog'u Cikti: .claude/shared/swarm-phase2-backend.md Sorulari: .claude/shared/swarm-questions.md'ye yaz ``` ### Agent 5: frontend-dev (Aria) ``` Gorevi: UI components, pages, state management implement et. Input: Phase 1 sentezi + Designer ciktisi (varsa) Cikti: .claude/shared/swarm-phase2-frontend.md Sorulari: .claude/shared/swarm-questions.md'ye yaz ``` ### Agent 6: designer (Marcus) ``` Gorevi: Design system, component specs, color/typography kararlari. Input: Phase 1 sentezi Cikti: .claude/shared/swarm-phase2-designer.md ``` ### Agent 7: devops (Kai) ``` Gorevi: CI/CD, Docker, deployment config, monitoring. Input: Phase 1 sentezi Cikti: .claude/shared/swarm-phase2-devops.md ``` Phase 2 tamamlaninca: 1. Sorulari oku (.claude/shared/swarm-questions.md) 2. Cevaplanmamis sorulari ilgili agent'a yonlendir 3. Cevaplari .claude/shared/swarm-answers.md'ye yaz 4. Catismalari coz ## Adim 5: Phase 3 - Paralel Review Tum Phase 2 ciktilarini 4 review agent'a ver: ### Agent 8: code-reviewer ``` Gorevi: Kod kalitesi, best practices, maintainability. Cikti: .claude/shared/swarm-review-code.md ``` ### Agent 9: security-analyst (Zara) ``` Gorevi: OWASP top 10, secrets, input validation, auth. Cikti: .claude/shared/swarm-review-security.md ``` ### Agent 10: qa-engineer (Priya) ``` Gorevi: Test stratejisi, edge cases, test plani yaz. Cikti: .claude/shared/swarm-review-qa.md ``` ### Agent 11: data-analyst (Yuna) ``` Gorevi: Analytics events, metrik tanimlama, A/B test plani. Cikti: .claude/shared/swarm-review-data.md ``` Phase 3 tamamlaninca: Review bulgularini topla, CRITICAL olanlari listele. ## Adim 6: Phase 4 - Duzeltme + Test Review'dan gelen CRITICAL ve HIGH bulgulari duzelt: ### Agent 12-13: backend-dev + frontend-dev ``` Gorevi: Review fix'lerini implement et. Input: Phase 3 review bulgulari ``` ### Agent 14: tdd-guide ``` Gorevi: QA engineer'in test planina gore testleri yaz. Input: Phase 3 QA ciktisi + Phase 2 implementasyon ``` ### Agent 15: verifier ``` Gorevi: Son quality gate - build, test, lint, security. Input: Tum Phase 4 ciktilari Cikti: PASS / FAIL raporu ``` ## Adim 7: Phase 5 - Finalizasyon ### Agent 16: self-learner ``` Gorevi: Tum swarm'dan ogrenimleri cikar, CLAUDE.md'ye kaydet. Input: Tum phase ciktilari + review bulgulari ``` ### Agent 17: technical-writer (Noah) ``` Gorevi: README, API docs, changelog guncelle. Input: Phase 2 implementasyon + Phase 1 mimari ``` ### Agent 18: growth (Camille) [opsiyonel] ``` Gorevi: Launch notu, feature announcement, GTM. Input: Phase 1 + Phase 5 docs ``` ## Swarm Raporu Her swarm sonunda su raporu uret: ```markdown # SWARM RAPORU Gorev: <gorev> Tarih: <tarih> Sure: <toplam sure> ## Katilimcilar | Agent | Phase | Durum | |-------|-------|-------| | scout | 1 | Tamamlandi | | ... | ... | ... | ## Iletisim Ozeti - Toplam soru: X - Cevaplanan: Y - Catisma cozulen: Z ## Review Bulgulari - CRITICAL: X (hepsi cozuldu) - HIGH: Y (Z tanesi cozuldu) - MEDIUM: W ## Verifier Sonucu PASS / FAIL ## Ogrenimler - <self-learner ciktisi> ## Sonraki Adimlar - <kalan isler> ``` ## Kurallar 1. Her phase bitmeden sonrakine gecme 2. CRITICAL review bulgulari MUTLAKA duzeltilmeli 3. Verifier FAIL verirse Phase 4'e don 4. Agent'lar arasi catismada maestro karar verir 5. Her agent kendi alaninin disina karismasin 6. Paralel calistirilabilecek agent'lari MUTLAKA paralel calistir
Related Skills
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity
tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.