One document per feature design, in English. The status column says how far each design has come.
| Status | Design | Tracking |
|---|---|---|
| Implemented | Data directory layout — global home + per-project partitioning | #374 |
| Implemented | Unified dashboard — four-module local dashboard | — |
| Implemented | GitCode provider | #361 |
| Implemented | Model profiles — teamai models |
— |
| Implemented | Team env by directory — each directory's shell gets the env of the scope that governs it | #1018 |
| Implemented | Assigned roles — manifest/members.yaml decides a member's roles |
#1186 |
| Implemented | Workspace children — a workspace also delivers what the repos set up inside it select | #913 |
| Implemented | Skill serving — built-in skill content shipped with the CLI (teamai skill get) |
#678 |
| Implemented, living | Team secrets — describes only what the current version does | #875, #879 |
| In progress | Multi-project management — project as a dimension orthogonal to role; P1/P2 shipped (--project, manifest/projects.yaml) |
#375 |
| Proposal | Management backend — a backend for members who do not use Git | #341 |
| Historical plan | Git-native memory — March 2026 planning note; recall and voting have since shipped and are documented in the Usage Guide | — |
| Historical plan | Team intelligence platform — March 2026 planning note; session docs, usage analytics and digest have since shipped | — |
Statuses:
- Implemented — the feature is in
main; the document explains the design behind it. - Implemented, living — the document is updated with every change and is the reference for current behavior.
- In progress — part of the phasing has shipped; the document says which.
- Proposal — describes future behavior; nothing in the CLI implements it yet.
- Historical plan — an early planning note kept for context. Current behavior is documented in the Usage Guide, not here.
Adding a design: one English file per feature, a > Status: line under the title, and a row in this table.