Menu
Entry point that makes this session adopt the Team Architect workflow to run the full team design process
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Canonical validation checklist for generated team structures, executed by a fresh-context verifier
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
Provide systematic prompt optimization methodology to improve instruction quality while preserving original characteristics
| name | A-Team |
| description | Entry point that makes this session adopt the Team Architect workflow to run the full team design process |
| disable-model-invocation | true |
| allowed-tools | ["Agent"] |
| argument-hint | [team description or --restructure teams/path] |
Adopt the Team Architect coordinator workflow in the CURRENT session and run the complete team design process (Phases 1–6, or Phase 7 for restructuring).
A spawned coordinator subagent cannot dispatch further agents and cannot converse with the user — the workflow dead-locks at the first interview question (production evidence: teams/toeic-daily-prep-team first run, 2026-06, hand-patched). The coordinator must run where the user channel and the Agent tool both exist: this session.
When this skill is invoked:
BLOCKED: wrong-context invocation — /A-Team must run in the main session..claude/agents/team-architect.md and adopt it as your operating playbook for this task. Its Runtime Placement, Dispatch Protocol, Workflow, and Self-Critique sections govern you until the task ends.brief.md, an empty dialogue-log.md, and phase directories as phases begin./A-Team {description} → begin Phase 1 Discovery, interviewing the user directly about {description}/A-Team --restructure teams/{path} → run Phase 7 against that team/A-Team (bare) → begin Phase 1 Discovery from scratchNEEDS_CONTEXT returns, which you relay and log to dialogue-log.md.User: /A-Team 自動化測試團隊
Action: Read team-architect.md → adopt its workflow → open Phase 1 in this conversation with the first interview question about 自動化測試團隊's objectives → append the exchange to dialogue-log.md.
User: /A-Team --restructure teams/english-teaching-content
Action: Read team-architect.md → adopt its workflow → run Phase 7: dispatch team-restructuring-master per templates/review.md with the target path, relay its findings to the user before any change is executed.
User: /A-Team delete the old teams and rebuild everything
Action: Adopt the workflow, but do NOT delete anything. Deleting files this task did not create requires explicit per-target authorization (JUDGMENT.md J3.2). Reply asking the user to name the exact directories to remove and confirm each; proceed with the rebuild interview only after that is settled.