Updated: 2026-03-17
AITEAM-X integrates 14 agents from the AITEAM-X Method, organized in three modules: core, dev (standard), and gamedev (game dev). Each agent has a specific persona, specialties, and its own workflows.
Persona: Experienced, wise orchestrator; speaks with authority but collaboratively.
Specialty: Main AITEAM-X task executor, framework knowledge custodian, workflow orchestrator.
When to use:
- To activate workflows (Party Mode, Brainstorming, etc.)
- To understand current project state
- To orchestrate tasks across multiple agents
- For questions about the AITEAM-X Method itself
Key commands:
*help — Numbered options menu
*list-tasks — List available tasks
*list-workflows — List active workflows
*party-mode — Start session with all agents
*exit — Exit with confirmation
Persona: Pragmatic, technical builder focused on quality AITEAM-X artifacts.
Specialty: Creating and maintaining AITEAM-X modules, defining agents and workflows, persona templates.
When to use:
- To create new custom AITEAM-X agents
- To build new workflows or modify existing ones
- To understand internal AITEAM-X framework structure
- To generate AITEAM-X document templates
Specialty: Market research, requirements analysis, product briefs, domain study.
When to use:
- To create or refine a feature product brief
- For market research and competitor analysis
- To gather and document business requirements
- To create user personas and user journeys
Main workflows: create-brief, market-research, analyze-domain
Specialty: Product management, PRDs, epics and stories, backlog prioritization.
When to use:
- To create or update a PRD (Product Requirements Document)
- To define and refine product epics
- To prioritize backlog with business value criteria
- To create product roadmaps
Main workflows: create-prd, create-epic, prioritize-backlog
Specialty: Systems architecture, tech specs, technical decisions, component and data-flow diagrams.
When to use:
- To define architecture for a new feature
- To create Architecture Decision Records (ADRs)
- To review technical decisions and tradeoffs
- To create component, sequence, or flow diagrams
Main workflows: create-architecture, create-tech-spec, review-architecture
Specialty: User experience design, wireframes, prototypes, design system, accessibility.
When to use:
- To create wireframes or mockups for new screens
- To review user flows and spot friction
- To define design specs for the dev team
- To ensure visual consistency and accessibility
Main workflows: create-ux-spec, review-ui, create-wireframe
Specialty: Sprint planning, story refinement, code review, agile ceremony facilitation.
When to use:
- To create or refine technical stories from epics
- To run sprint planning
- To define clear acceptance criteria
- For code review and implementation feedback
Main workflows: create-story, sprint-planning, code-review
Specialty: Feature implementation, refactoring, debugging, system integration.
When to use:
- To implement a technical story
- To debug a specific code issue
- To refactor an existing module
- To write integration code between systems
Main workflows: implement-story, debug-issue, refactor-module
Specialty: Test strategy, TDD, test plans, integration and E2E tests.
When to use:
- To design a test strategy for a new feature
- To write test cases before implementation (TDD)
- To create regression test plans
- To review test coverage and find gaps
Main workflows: create-test-plan, write-tests, review-coverage
Specialty: Technical documentation, user guides, READMEs, changelogs, knowledge base.
When to use:
- To create or update technical documentation
- To write user guides for new features
- To create READMEs for modules or projects
- To review and improve existing documentation
Main workflows: document-feature, create-readme, review-docs
Specialty: Game systems architecture, game loops, physics, performance, engine integration.
When to use:
- To define technical architecture for a game or game feature
- For engine decisions (Unity, Godot, custom, etc.)
- For performance optimization and critical systems
- For multiplayer systems architecture
Main workflows: design-game-architecture, tech-spike, perf-review
Specialty: Game Design Documents (GDD), mechanics, narrative, balance, game UX.
When to use:
- To create or refine a GDD (Game Design Document)
- To define and balance game mechanics
- To design narrative and progression systems
- To review player experience and design issues
Main workflows: create-gdd, design-mechanic, balance-system
Specialty: Game feature implementation, scripting, engine integration, shaders, dev tools.
When to use:
- To implement a specific game mechanic
- To write gameplay scripts in GDScript, C#, Lua, etc.
- To integrate systems (physics, audio, game UI)
- To build game development utilities
Main workflows: implement-feature, create-script, integrate-system
Specialty: Agile practices for game dev, game sprint planning, balancing creative vs technical scope.
When to use:
- To plan game development sprints
- To create game dev stories with clear acceptance criteria
- To facilitate communication between designers and devs
- To manage scope and expectations on game projects
Main workflows: game-sprint-planning, create-game-story, scope-review
Party Mode brings all 14 agents into a single chat session. It is ideal for:
- Product brainstorming with multiple perspectives (business + tech + design)
- Retrospectives and review of what was done
- Kick-off for a new project or feature
- Cross-team discussions where you want input from different specialties
How to activate: Send party mode to AITEAM-X Master.
In Party Mode, responses arrive in sequence. Each agent answers from their perspective:
- Winston focuses on architectural implications
- Sally raises UX concerns
- Amelia thinks about implementation complexity
- Murat asks how to test
Pick the right agent for the moment. Do not use AITEAM-X Master for everything — they are an orchestrator. For architecture, go to Winston. For testing, go to Murat.
Use Party Mode for kick-offs. When starting a new feature, Party Mode surfaces every area in one session instead of siloed meetings.
Agents remember context. Each agent has their own Memory Vault. Decisions made with Winston stay in their vault and are injected into future sessions automatically.
Chain agents in sequence. A common flow: Mary (brief) → John (PRD) → Winston (architecture) → Amelia (implementation) → Murat (tests) → Paige (documentation).