7. Teams
Categories
| Category | What a team in this category does | What it does not include |
|---|---|---|
| Asteroid | A few roles and documents only: no product is built. For incubating ideas, briefs and vision. | Requirements, design and code. |
| Nebula | A definition team: product, analysis, design, test cases and technical design. Code and testing happen outside the app; the workflow goes on hold until you confirm it is implemented and tested. | Code and testing. |
| Supernova | A full team that builds and tests the product from the app. No deployments: the approved version is handed over to be published elsewhere. | Deployments. |
| Galaxy | A full team with DevOps: it builds, tests, deploys and publishes the product on the internet, configuring servers, environments and monitoring. Requires a license that includes it. | — |
| Moon | Teams that help with the working process and with the app itself. Requires a license with own teams. The app does not ship any for now. | Building a product. |
| Comet | Your own teams: the ones you create in AI Teams or import. Requires a license with own teams. | — |
The Asteroid, Nebula, Supernova, Galaxy and Moon categories are reserved for the teams shipped with the app, which are signed. An own team cannot declare them.
Teams shipped with the app
They all have the same shape: team/AI_TEAM_CORE.md (the flow), one document per role in team/roles/, one participation sheet per role and the shared procedures in team/flow/, and team/CHANGELOG.md with the version history (the agent does not read it to work). The core does not repeat what is already in the sheets (the handoffs) or in the changelog, so that each role activation loads just what it needs.
All of them exist in Spanish and in English.
| Team | Category | Roles | Workflow | Recommended for |
|---|---|---|---|---|
| Ceres — Project Incubator | Asteroid | Product Strategist | Incubation in 4 phases and 8 steps: exploration, refinement, assumption validation, Vision Document and close. You confirm each phase close; at the end the team tells you how to continue with a development team (Change team…). | Product ideas that are not defined yet. It is the step before a development team: its Vision Document is the input for Sprint 0. |
| Orion — Product definition team | Nebula | Business Analyst, Product Owner, UI/UX Designer, QA and Software Architect | Sprints of 5 phases (Sprint 0, Definition, Design, On hold and Sprint close) and 15 steps with checkpoints that you approve with buttons. Each sprint defines a feature and hands it to the external team that implements it; the sprint closes as “handed over, on hold” and meanwhile you can define the next one. At the start of a sprint, or with the Resume after the wait button, the deliveries already implemented and tested are reviewed. If you prefer to build inside the app, you can move to Vela with Change team…. | Products or features implemented by another team (an external company, an internal team or yourself) where you want a complete, reviewable definition before coding. |
| Vela — Complete Product Team | Supernova | Business Analyst, Documentador, Full Stack Developer, Product Owner, QA, Software Architect and UI/UX Designer | Sprints of 5 phases (Sprint 0, Definition, Design, Build, Delivery and closing) and 25 steps with checkpoints: you approve each deliverable with buttons before the next role takes over. It ends with the handover of the approved version, not its deployment: you publish it, or you move to Andromeda with Change team…. The Report incident button starts the triage of a problem in an already published version. | Products or apps that will actually be built, from Sprint 0 to production, with or without AI. Works for one person holding every role or for a team that shares them. |
| Andromeda — Product team with DevOps | Galaxy | Business Analyst, Documentador, Full Stack Developer, Product Owner, QA, Software Architect, UI/UX Designer and DevOps | Sprints of 4 phases (Sprint 0, Planning, Build, Delivery and closing) and 25 steps with checkpoints that you approve. DevOps deploys to test and production and publishes the service (domain, certificates, monitoring); the Report incident button starts the triage of a problem in the published version. | Products that will really be built and published on the internet, with environments, deployments and rollback. |
Each team also comes with quick buttons for the chat (for example, in Vela: Backlog, Project status, Consistency audit, Generate Document, Improvements).
Prometheus, the Moon team that created teams, no longer ships with the app: teams are now created in AI Teams, with their dedicated screen and the agent. A project created earlier with Prometheus still opens and works with the copy of the team in its folder; since the app no longer ships that team, it is not offered in Change team… and no new versions are proposed. The .tacteam packages it generated can still be imported.
Your own teams (import)
With a license that includes Own teams, you can import a team created outside the app:
- In the AI Teams tab, open Import ▾ (in the adoption and change-team wizards, the + Import your own team button in the teams header). The check and the report are shown above the list.
- Choose a .tacteam file (a team package, like the ones exported from AI Teams) or a team folder (with
team-ai-console.json, the workflow and the role documents). - The app checks the team before importing it and shows a report:
- Errors — they prevent the import (for example, a role document that does not exist or a reserved category).
- Warnings — they do not prevent the import (for example, a team without a version).
- For each language: roles, steps, phases and files.
- If you had already imported that team: whether it is an update (higher version), an identical version, an older version, or the same version number with different content, and how many files change.
- If the id matches a team shipped with the app, it proposes importing it with another id.
- Click Import (or Update, Import again, Import as… depending on the case).
If the chosen folder has team documents but no configuration, the app offers to analyze it with the agent (Claude Code or Codex) to propose the configuration (the agent only reads; the app validates and writes the files). It uses the agent chosen in the team editor or, if you haven’t chosen one, the one you are signed in to.
Imported teams stay on your computer, in your list of teams, with their version next to the name (and the Imported label in the wizards, or on the home-screen card when the team does not say what it is for; their origin, under Details). On the home screen they are managed from Teams and Roles (AI Teams section); in the wizards, the ⋯ menu on their card offers:
- Import a new version…
- Restore the previous version (x.y.z) — if you updated, the previous version is kept as a backup.
- Show folder.
- Remove from the list — projects already created with that team do not change.