Repository navigation
TeamAI Roadmap #647
Description
- Documentation, Website & Templates
- Simplify the README and organize documentation into clear layers.
- Build the TeamAI website as a central hub for documentation and templates.
- Expand the template repository with ready-to-use scenario templates.
- Team Execution
- Refine project binding, resource distribution, and switching in Projects.
- Support workflow definition and distribution.
- Improve and expand support for different Agents.
- Team Context
- Define a Connector protocol to integrate data sources and knowledge bases, including WeCom Docs, Tencent Meeting, and Google Drive.
- Improve Recall’s recall and precision, and strengthen feedback mechanisms.
- Team Improvement
- Add Skill health checks.
- Improve knowledge capture, promotion, updates, and archiving.
- Fix Agent data collection and reporting issues.
- Dashboard
- Display key metrics and trends.
- Show the sources, versions, and activation status of locally installed resources.
- Support resource editing, validation, and review-based publishing.
Activity
shusun-lu commentedon Sep 24, 2026
Reviewer-side checks for
teamai/push/*branchesTwo items on this roadmap are things I ran into while using teamai:
4. Team Improvement → "Add Skill health checks" and
5. Dashboard → "Support resource editing, validation, and review-based publishing".
I use teamai against a self-hosted Git host where the provider cannot open a PR/MR, so
teamai pushonly creates
teamai/push/<user>/<timestamp>. Everything after that is manual: nothing tells mewhether what I just pushed is actually usable. I ended up writing a small local reviewer.
I opened #776 with the concrete proposal — a read-only check (structure, naming, cross-namespace
duplicate names, format, leaks;
fail/warn/info;--json) and the open questions.The one thing I would like your opinion on first: where should it live — extending
teamai reviewfeels closest in spirit, but a flag on
push/statusmay fit the CLI better. No auto-merge in theproposal. Happy to send a PR in whatever shape you prefer, reusing the existing parsers and
utils/redactrather than a second implementation.jeff-r2026 commentedon Sep 24, 2026
Thanks for grounding this in a real workflow, and for opening #776 with a concrete, read-only proposal.
On the entry point: please do not extend
teamai review. That command already means inspect/apply/reject items in.teamai/pending-review.jsonl. Mixing branch health checks into it would collide with that meaning.Prefer a shared checker (reuse the existing parsers and
utils/redact, no second implementation) with:teamai doctoras the primary, read-only entry (it already reports +--json+ non-zero exit for CI), targeting ateamai/push/*branch or a checkoutteamai pushso the author gets the same signal before the branch is left for a human mergestatusshould stay “local vs team repo diff”. No auto-merge / publish in this slice; merging stays a human decision.On the default
failset, your list looks right: missingSKILL.md, missing/mismatched frontmattername, cross-namespace duplicates that would breakpull, undeclared namespace, and a credential hit. The rest can bewarn. Conventions stay opt-in.A PR against #776 in that shape is welcome, including a real-CLI e2e record. Happy to discuss details on #776 so this roadmap thread stays a pointer.
[-]TeamAI Roadmap Discussion — We’d Love to Hear Your Thoughts![/-][+]TeamAI Roadmap[/+]11 remaining items
learnings/to ateamai-learningsbranch (direct push, no PR) #485