open-teams
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 7 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
open-teams: AI collaboration workspace template for Cursor, Copilot & Claude Code. Git-native AGENTS.md, MEMORY.md, Skills & task plans — make AI a first-class teammate.
English | 中文
open-teams
open-teams — AI collaboration workspace template for Cursor, Copilot & Claude Code.
Git-native AGENTS.md, MEMORY.md, Skills & task plans turn AI from a one-shot chat into a first-class teammate.
Quick Start • Why? • Features • Structure • Comparison • Roadmap • Discussions
Why open-teams?
Your team loves AI coding tools. Cursor, GitHub Copilot, Claude Code — everyone's using them. Productivity is up. But after a few sprints, you notice something:
- Context vanishes. Every new AI chat starts from zero. Yesterday's architecture decision? Gone.
- Standards diverge. Five team members, five different Cursor rules. Code review is a style-war zone.
- Knowledge leaks. Wang's killer prompt lives in his chat history. Li's debugging trick stays in her DMs. Nobody else benefits.
- Onboarding is manual. Every new hire re-teaches AI from scratch. Two weeks before they're productive.
The problem isn't the AI. It's the layer between the AI and the team.
Who it's for: engineering teams that want a shared AI workspace template — one Git repo for team constitution (AGENTS.md), long-term memory (MEMORY.md), modular Skills, and task plans — without locking into a single AI vendor.
open-teams is that layer — a lightweight, Git-native workspace template that gives your AI:
- 🧠 Memory — so it remembers what happened last session (
MEMORY.md+ daily notes) - 📋 Shared Standards — so everyone's AI follows the same
AGENTS.mdrules - 🔌 Modular Skills — reusable workflows for code review, API design, architecture review
- 📝 Knowledge Capture — so insights become team assets, not lost chat history
"Not a new AI tool. An operating system for how your team collaborates with AI."
Architecture Overview
┌──────────────────────────────────────────────────────────┐
│ Your AI Coding Tool │
│ (Cursor / Copilot / Claude Code / ...) │
└─────────────────────┬────────────────────────────────────┘
│ reads & writes
▼
┌──────────────────────────────────────────────────────────┐
│ open-teams Workspace │
│ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────┐ │
│ │ AGENTS.md │ │ MEMORY.md │ │ TOOLS.md │ │
│ │ Team │ │ Long-term │ │ Environment- │ │
│ │ Constitution│ │ Memory │ │ specific Notes │ │
│ └─────────────┘ └──────────────┘ └─────────────────┘ │
│ │
│ ┌───────────────────────────────────────────────────┐ │
│ │ Skills (Modular AI Workflows) │ │
│ │ ┌──────────┐ ┌──────────┐ ┌──────────────────┐ │ │
│ │ │code- │ │api-design│ │architecture- │ │ │
│ │ │review/ │ │-review/ │ │review/ │ │ │
│ │ │SKILL.md │ │SKILL.md │ │SKILL.md │ │ │
│ │ │rules/ │ │rules/ │ │rules/ │ │ │
│ │ │examples/ │ │examples/ │ │examples/ │ │ │
│ │ └──────────┘ └──────────┘ └──────────────────┘ │ │
│ └───────────────────────────────────────────────────┘ │
│ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────┐ │
│ │ docs/ │ │ memory/ │ │ task-plans/ │ │
│ │ Team Docs │ │ Daily Notes │ │ Sprint Plans │ │
│ └─────────────┘ └──────────────┘ └─────────────────┘ │
└──────────────────────────────────────────────────────────┘
│ version controlled
▼
┌──────────────────────────────────────────────────────────┐
│ Git Repository │
│ AI rules, memory, and skills — reviewed in PRs like code │
└──────────────────────────────────────────────────────────┘
Key insight: AI reads Markdown natively. Git tracks everything. Your AI's "brain" gets the same rigor as your codebase.
Features
| Feature | Description | Impact |
|---|---|---|
| 🧠 AGENTS.md | Team constitution file — project context, tech stack, conventions, red lines. Read by AI on every session. | Eliminates repetitive context-setting |
| 📝 MEMORY.md | Long-term AI memory — key decisions, lessons learned, architecture rationale. Curated, not raw logs. | AI "remembers" across sessions |
| 🔌 Skills | Modular, pluggable AI workflows with rules, checklists, and examples. Trigger on-demand. | Standardize code review, API design, architecture review |
| 📋 memory/ | Daily collaboration logs — raw records of what happened. AI helps maintain them. | Process visibility and traceability |
| 🛠️ TOOLS.md | Environment-specific configuration — per-project, per-team notes. Not shared between contexts. | Clean separation of global vs. local config |
| 🔄 Git-Native | All AI assets live in Git. PRs for rule changes. Diff for memory updates. | Version control for AI behavior |
| 🔓 Tool-Agnostic | Works with Cursor, Copilot, Claude Code, Continue.dev, and any AI tool that reads files. | No vendor lock-in |
| 💬 Dialogue adoption | AI-guided workspace setup via QUICKSTART.md and adopt_workspace.py — no shell wizard required. |
Zero-friction, structure-safe adoption |
| 🌐 en/ + zh/ | Complete English and Chinese workspaces — pick a language, open that folder, adopt that tree. | First-class bilingual retention |
Quick Start
Prerequisites
- Git installed
- Any AI coding tool (Cursor, Copilot, Claude Code, etc.)
- 5 minutes
Setup
This repository is a monorepo template with two complete workspaces:
| Path | Language | Open in Cursor / AI tools |
|---|---|---|
en/ |
English | Open en/ as the workspace root |
zh/ |
中文 | Open zh/ as the workspace root |
# 1. Clone the template (keep as read-only reference)
git clone https://github.com/struggling-bird/open-teams.git open-teams-template
# 2. Open the English workspace (or use zh/ for Chinese)
cursor open-teams-template/en
# 3. Adopt into your business workspace (run from the repo root)
python3 open-teams-template/scripts/adopt_workspace.py \
--template-root open-teams-template \
--target /path/to/your-workspace \
--project-slug my-app \
--project-name "My App" \
--source-path /path/to/source \
--default-branch main \
--adoption-mode ai-guided \
--workspace-language en
# 4. Open the target folder in your AI tool and finish MEMORY.md / AGENTS.md
Use --workspace-language zh to copy the Chinese workspace instead. Full walkthrough: en/QUICKSTART.md · zh/QUICKSTART.md · en/docs/getting-started.md.
That's it. Your AI now:
- ✅ Knows your project structure and tech stack (from
AGENTS.md) - ✅ Remembers past decisions (from
MEMORY.md) - ✅ Follows shared review standards (from
skills/) - ✅ Writes daily collaboration notes (in
memory/)
Try your first Skill
# Open your AI tool in the adopted workspace (or en/), then prompt:
"Review the latest commit using the code-review skill"
The AI reads skills/code-review/SKILL.md, loads the checklist and rules, and delivers a structured review — every team member gets the same quality standard.
English retention path
- This README +
en/QUICKSTART.md en/docs/getting-started.md- Governance contracts:
en/AGENTS.md,en/workspace-assets-index.md,en/task-completion-checklist.md,en/MEMORY.md - Chinese docs:
zh/README.md
Project Structure
open-teams/
├── README.md # You are here — GitHub landing (English)
├── LICENSE · CHANGELOG.md · CONTRIBUTING.md · SECURITY.md
├── .github/ # CI, issue & PR templates
├── scripts/adopt_workspace.py # Copy en/ or zh/ into a new workspace
├── assets/logo.svg
│
├── en/ # Complete English workspace ← open this in Cursor
│ ├── AGENTS.md # Team constitution — AI reads this first
│ ├── MEMORY.md # Long-term team memory
│ ├── QUICKSTART.md # Dialogue-guided adoption
│ ├── skills/ # Modular AI capabilities
│ │ ├── _workflow/ # Cross-project process gates
│ │ ├── code-review/
│ │ ├── api-design-review/
│ │ ├── architecture-review/
│ │ └── onboarding/
│ ├── docs/ # Architecture, specs, getting-started
│ ├── workspace-config/
│ ├── task-plans/ · change-history/ · memory/ · sources/
│ └── scripts/ # validate / health-check / cleanup
│
└── zh/ # Complete Chinese workspace ← 中文请打开这里
├── AGENTS.md
├── MEMORY.md
├── QUICKSTART.md
├── skills/ · docs/ · workspace-config/ · …
└── …
Comparison
open-teams vs. Raw AI Chat vs. Traditional Project Management
| Dimension | Raw AI Chat | Shared Rules File | Notion/Confluence Docs | ✅ open-teams |
|---|---|---|---|---|
| Context persistence | ❌ Lost when chat ends | ⚠️ One flat file, no structure | ❌ AI can't read Notion | ✅ Multi-layer: AGENTS.md + MEMORY.md + daily logs |
| Team alignment | ❌ Everyone teaches AI differently | ⚠️ Single-file contention | ⚠️ Docs exist, but AI ignores them | ✅ Git-managed shared standards |
| Knowledge capture | ❌ Scattered in chat histories | ❌ No structured capture | ⚠️ "Result docs," not process | ✅ Daily logs + curated long-term memory |
| Skill reusability | ❌ Every session starts fresh | ❌ Copy-paste between projects | ❌ Docs ≠ executable workflows | ✅ Modular Skills — install and reuse |
| Tool independence | ❌ Tied to one chat tool | ⚠️ Usually tool-specific | ⚠️ Platform-dependent | ✅ Works with any file-reading AI |
| Version control | ❌ No history | ⚠️ Basic Git tracking | ❌ Notion versioning is limited | ✅ Full Git: diff, PR review, blame |
| Onboarding speed | ❌ Weeks of oral tradition | ⚠️ Read the rules file | ⚠️ Read the wiki | ✅ Clone → AI knows the team |
| Review standardization | ❌ Each reviewer has own bar | ⚠️ One checklist fits all | ⚠️ Checklist exists, manual usage | ✅ Skill-embedded review rules |
open-teams vs. Competitors (Detailed)
| Tool | Best For | Limitation |
|---|---|---|
| Copilot Rules | Individual AI coding efficiency | Single-file, no team sharing, tool-locked |
| Notion AI | Non-technical knowledge management | AI doesn't natively read Notion in your IDE |
| Cursor Rules | Per-project cursor configuration | Not modular, not shared across tools |
| open-teams | Dev team AI collaboration at scale | Requires Git basics (not for non-tech teams) |
Roadmap
| Version | Status | Highlights |
|---|---|---|
| v0.1 – v0.4 | ✅ Done | Core template, AGENTS.md governance, 4 core Skills + 6 workflow Skills, CI/CD, template validation |
| v0.5 | ✅ Done | Unified dialogue-guided adoption; removed legacy init.sh |
| v0.6 | 🚧 In progress | Complete en/ + zh/ workspaces; bilingual retention & GitHub discoverability |
| v0.7 | 📋 Planned | VS Code extension, CLI tool enhancements |
| v1.0 | 📋 Planned | Skills marketplace, team analytics, enterprise features |
💡 Have a feature idea? Open a Discussion.
Contributing
open-teams is community-first. Whether you're fixing a typo or proposing a new Skill, you're welcome.
Ways to Contribute
- ⭐ Star the repo — it helps more people find us
- 🐛 Report bugs — Open an Issue
- 💡 Suggest features — Start a Discussion
- 🔧 Submit PRs — See CONTRIBUTING.md
- 📖 Improve docs — Keep
en/andzh/in sync when changing governance or install guides - 🧩 Share Skills — Built a useful Skill? Share it with the community
- 🌍 Translate — Help localize docs for global teams
Good First Issues
Check out issues labeled good first issue — we'll help you through your first PR.
Community
- 💬 GitHub Discussions — Questions, ideas, RFCs
- 📢 Follow for updates (links coming soon)
Star History
License
MIT © struggling-bird
Built with ❤️ by developers who believe AI should augment teams, not replace them.
⭐ Star us on GitHub
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found