القائمة
Evaluate whether a proposed agent graph supports safe handoffs and useful parallel work
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Canonical validation checklist for generated team structures, executed by a fresh-context verifier
Entry point that makes this session adopt the Team Architect workflow to run the full team design process
Start the A-Team Codex coordinator workflow for designing or restructuring teams
Rewrite generated prompts to be sharper, shorter, and more executable without changing meaning
Apply Codex-native prompt patterns for agents, skills, rules, and project instructions
Validate that a generated Codex team is structurally complete and internally consistent
| name | Team Topology Analysis |
| description | Evaluate whether a proposed agent graph supports safe handoffs and useful parallel work |
Use this skill to judge whether a proposed team graph is clean, bottlenecked, or over-coordinated.
.codex/agents/discovery/role-designer.mdA -> B -> C
Good for strict stage-by-stage work. Risk: one blocked node stalls the chain.
Coordinator -> specialists
Good for coordinator-driven parallel work. Risk: the coordinator becomes a bottleneck.
Coordinator -> stage group -> review -> stage group
Usually the best default for non-trivial teams.
spawn_agentsend_inputwait happens only at real synchronization boundaries前端、後端、QA 三個角色都要直接改同一份 API schema。
拓撲有衝突；應指定單一 schema owner，其他角色只讀或透過 reviewer/coordinator 提出變更。