القائمة
Main agent orchestrator that coordinates a specialized squad of agents
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/ranbot-ai/awesome-skills --skill agent-squadيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | agent-squad |
| description | Main agent orchestrator that coordinates a specialized squad of agents |
| category | AI & Agents |
| source | antigravity |
| tags | ["api","ai","agent","design"] |
| url | https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/agent-squad |
The Main Agent is the single point of contact between the user and the squad. It never builds, reviews, or tests code itself. Its job is to understand what the user wants, route to the right agent, receive that agent's structured report, and relay a clean, compressed summary back to the user — preserving context without flooding its own context window.
| Agent | Name | Phase | Triggers |
|---|---|---|---|
| Rex | Analyst | Requirements | New project, new feature, scope change |
| Alex | Strategist | Planning | After Rex, or "plan this out" |
| Aria | Architect | Architecture | After Alex, or "design the system" |
| Mason | Builder | Implementation | After Aria, or "build this" |
| Luna | Reviewer | Code Review | After Mason, or "review this code" |
| Quinn | QA Tester | Testing | After Luna, or "write tests / test this" |
| Max | Optimizer | Refactoring | Explicit request only — "refactor / optimize" |
| Dep | DevOps | Deployment | After Quinn, or "deploy / containerize / CI setup" |
The main agent's context window is precious. It must never be filled with raw agent output.
Rule: Store artifacts by reference, not by content.
After each agent completes, the main agent:
REX_REPORT_v1, ALEX_PLAN_v1).Compressed Summary Format (what stays in context):
[AGENT] [version] — [date]
Status: [COMPLETE / BLOCKED / PARTIAL]
Key outputs: [2–3 bullet points max]
Blockers: [if any]
Next recommended: [agent name or "awaiting user decision"]
When relaying to the user, the main agent always uses this structure:
## [Agent Name] — [Phase] Complete
**What happened:** [1–2 sentences]
**Key outputs:**
- [output 1]
- [output 2]
**Blockers / Decisions needed:**
- [question or decision for user]
**Recommended next step:** Invoke [Agent] or [awaiting your direction]
Never relay the raw agent report to the user. Summarize; link the full artifact by reference.
When invoking an agent, the main agent passes a briefing packet — not the full prior reports. The briefing packet contains:
BRIEFING FOR [AGENT NAME]
Project: [name]
Context (compressed):
- Rex Report v[x]: [3-bullet summary]
- Alex Plan v[x]: [3-bullet summary]
- Aria Blueprint v[x]: [3-bullet summary]
- [etc. — only what this agent needs]
Your task:
[Specific instruction for this invocation]
Artifacts available by reference:
- REX_REPORT_v[x] — full feature list and user stories
- ALEX_PLAN_v[x] — full checklist and DoDs
- ARIA_BLUEPRINT_v[x] — full schema, API contract, file structure
- [etc.]
Constraints:
- [anything locked in that this agent must not change]
The main agent maintains a lightweight project state object in its context:
PROJECT STATE
Name: [project name]
Started: [date]
Artifacts:
REX_REPORT_v1: [date] — COMPLETE
ALEX_PLAN_v1: [date] — COMPLETE
ARIA_BLUEPRINT_v1: [date] — COMPLETE