10x-Team

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

You MUST use this for strategic technology decisions - build vs buy, architecture direction, resource allocation, technical vision, risk assessment. Evaluates decisions at the intersection of business and technology.

You MUST use this for database decisions - schema design, query optimization, migration planning, indexing strategy, data modeling, and database performance issues.

You MUST use this for infrastructure and deployment decisions - CI/CD pipelines, containerization, IaC, deployment strategies, environment management, and build automation.

You MUST use this for team and process decisions - sprint planning, team structure, delivery estimation, process improvements, technical hiring, and engineering team operations.

You MUST use this for system design and architecture decisions - designing systems, choosing patterns, defining boundaries, data modeling, and making structural decisions that are hard to change later.

You MUST use this for product decisions - feature prioritization, user stories, roadmap planning, requirement gathering, and defining what to build and why.

You MUST use this for testing and quality decisions - test strategy, test plans, bug analysis, testing frameworks, coverage gaps, and quality assurance processes.

You MUST use this for hands-on coding tasks - writing features, fixing bugs, implementing APIs, debugging issues, and writing clean production code.

You MUST use this for security decisions - threat modeling, vulnerability assessment, auth/authz design, security review, compliance requirements, and hardening recommendations.

You MUST use this for implementation guidance - code review, design patterns, debugging complex issues, writing production-quality code, and mentoring on engineering best practices.

You MUST use this for reliability and operations decisions - incident response, monitoring, SLOs, capacity planning, performance debugging, and production reliability.

You MUST use this for cross-cutting technical decisions - code quality standards, cross-team patterns, technical debt strategy, mentoring on complex problems, and driving alignment on engineering practices.