team-sync
/team-sync
Use when 2+ humans or AI agents work in parallel — file ownership, branching, avoiding merge conflicts, and patterns for collaborating with AI tools as a group.
- Author
- lukashouthoofd ↗
- Repository
- cenekathon ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when 2+ humans or AI agents work in parallel — file ownership, branching, avoiding merge conflicts, and patterns for collaborating with AI tools as a group.
Original author description
Use when 2+ humans or AI agents work in parallel — file ownership, branching, avoiding merge conflicts, and patterns for collaborating with AI tools as a group.
How it works
SKILL.md has no level-two headings · 14 lines, 211 words
SKILL.md preview
--- name: team-sync description: Use when 2+ humans or AI agents work in parallel — file ownership, branching, avoiding merge conflicts, and patterns for collaborating with AI tools as a group. --- # Team sync (parallel humans + agents) 1. **Ownership map** in `docs/TEAM.md`: person → folders/files → current task. One owner per file. Shared files (dependency manifest, lockfile, router index, `docs/PLAN.md`) → announce before editing. 2. **Contract first.** Before splitting front/back, agree the interface (route, JSON shape, function signature) in `docs/STACK.md` or a shared types file. Then both sides mock against it. 3. **Branches:** `<initials>/<task>`; start from fresh `main`; open a PR within 30–45 min; squash-merge. Pull `main` before every task and every ~30 min. 4. **Conflict rule:** whoever merges second resolves. Never force-push `main`. Never `git add -A` blindly — stage your own files. 5. **Agent hygiene:** one agent session per branch/worktree (`git worktree add ../wt-<task> -b <branch>`). Give each agent: the task, the files it may touch, the verification command. Tell it to stop and report rather than refactor neighbours. 6. **Shared context lives in files, not chat:** decisions → `DECISIONS.md`, status → issue comments. Agents re-read files; they forget conversations. 7. **Sync beat:** every 45 min, 3 minutes: done / doing / blocked. Update the cut line. 8. **Review:** skim for secrets, mocks presented as real, and anything that breaks `main`. Approve fast. **Done when:** no two people share an unplanned file and `main` still runs after every merge.
Versions
The database has no other skills named team-sync.
Database snapshot: 13.11.2026 · package version 018ca855efba (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100conflicts
Resolve git merge conflicts by analyzing change intent across branches. Use when the user asks to resolve merge conflicts, sync a branch, merge branches, or when a git merge produces conflicts.