izTeam

Orchestrates hypothesis-driven reasoning through the ADI cycle (Abduction-Deduction-Induction): generates competing hypotheses, verifies them logically, gathers empirical evidence, and produces a Design Rationale Record with trust scores. Use when facing architectural decisions, technology choices, or any question where "why this and not that" matters. Don't use for quick questions, implementation, expert debates (use /arena), or structured thinking without evidence requirements (use /think).

Orchestrates multi-expert debates with real-world personas who argue directly with each other until convergence. Use when the user wants multiple opposing viewpoints, expert panel discussion, or structured debate on a complex question. Don't use for quick questions, single-expert analysis, implementation planning, or structured thinking without debate.

Launches an autonomous agent team for coordinated multi-file implementation with researchers, coders, reviewers, and a tech lead. Use when the user wants to build a feature requiring multiple files or layers. Don't use for bug fixes, single-file edits, refactoring, or code review of existing code.

Conducts an interactive feature audit to find dead code, abandoned experiments, and unused features, then asks the user about each one. Use when the user wants to clean up the codebase, find unused code, or review experimental features. Don't use for security audits, performance profiling, dependency scanning, or code quality reviews.

Conducts a short adaptive interview (2-6 questions) to understand the user's intent before implementation, then compiles a brief and hands off to /build. Use when the user asks to discuss a feature before building, wants to be interviewed first, or says 'ask me questions'. Don't use when the user already has a detailed spec, wants to jump straight into coding, or invokes /build directly.

Performs deep structured thinking by breaking a task into aspects, dispatching parallel expert analysts, and producing a unified design document with recommendations. Use when the user wants to think through a complex problem, plan an architecture, or analyze trade-offs before implementing. Don't use for implementation, quick questions, expert debates (use /arena), or simple tasks that don't need multi-aspect analysis.

Analyzes the codebase and creates or updates a .conventions/ directory with gold standards, anti-patterns, naming rules, and architectural decisions. Use when the user wants to extract project conventions, document coding standards, or bootstrap a conventions directory. Don't use for linting individual files, fixing code style, generating documentation, or creating project templates.