Stark-Han
2dbe97d5b6
* chore: ignore local agency and team snapshots * feat: add team agent profile templates * KANBAN * template * prototype * Fix tenant runtime pool deployment * Fix local team profiles runtime override * Update local team profiles testing guide * Adapt local team profiles test deployment * Patch tenant NFS server to ClusterIP * Use NFS export root for workspace mounts * Tighten team task completion projection * Fix team event body map comparison * before modification * temp_peer1 * leadermodel * team_fix * fix(team): harden workflow completion and workspace handling * fix(team): harden redis workflow protocol * discord link updated * chore: checkpoint team workflow fixes * fix: stabilize leader kanban ledger * fix: coalesce leader mediated work items * fix: confirm leader-mediated member results * fix: harden leader mediated team state * fix: stabilize team shared runtime state * Fix team task reconciliation and create flow * fix: stabilize leader mediated team orchestration * fix: refine team workspace presentation * checkpoint: persist team workflow ledger fixes * fix: reconcile team workflow delivery state * fix: preserve meaningful team chat events * docs: add team workspace quick guides * chore: ignore local team deployment files * fix: preserve setgid on team shared directories
51 lines
2.8 KiB
Markdown
51 lines
2.8 KiB
Markdown
# Team Workspace Quick Guide
|
|
|
|
Teams let multiple OpenClaw Lite members work toward one shared goal. Choose a role template, create the Team, then describe the goal to the Leader in Team chat. The Leader plans, delegates, coordinates, synthesizes, and delivers the final result.
|
|
|
|
## Scope
|
|
|
|
- Teams currently run in **OpenClaw Lite** mode.
|
|
- Collaboration is fixed to **Leader-mediated collaboration**: work reaches the Leader first, who coordinates the members.
|
|
- Templates already define member responsibilities. You normally do not configure a runtime, resource preset, or collaboration setting for every member.
|
|
|
|
## 1. Create a Team
|
|
|
|
1. Open **Teams** from the navigation and choose to create a Team.
|
|
2. Enter a Team name and adjust shared storage when needed.
|
|
3. Choose a member template and confirm the Leader, member count, and runtime in the summary.
|
|
4. Select **Create**.
|
|
|
|
|
|
|
|
The creation page fixes Teams to OpenClaw Lite and Leader-mediated collaboration. The selected template defines member responsibilities, so individual resource presets are not required.
|
|
|
|
## 2. Start Collaboration
|
|
|
|
Open the Team detail page and describe the business goal to the Leader in Team chat. For example: “Build a simple calculator app.”
|
|
|
|
The Leader creates the plan, assigns members, collects deliveries and review evidence, and publishes a final synthesis. You do not need to manually send the same task to every member.
|
|
|
|
## 3. Follow Progress
|
|
|
|
The Team detail page has two primary areas:
|
|
|
|
- **Team chat** shows plans, assignments, meaningful progress, deliveries, reviews, and Leader synthesis.
|
|
- **Execution Kanban** shows root-task state, pending work, active work, and completed deliveries.
|
|
|
|
|
|
|
|
States such as “Leader planning”, “waiting for member delivery”, and “waiting for Leader synthesis” indicate the current collaboration stage. Do not resend the same task; add a follow-up in chat if the goal or acceptance criteria change.
|
|
|
|
## 4. View Deliveries
|
|
|
|
Members return artifacts and validation conclusions to the Leader. The final synthesis appears in Team chat and task details. Use the **Files** tab at the top of the detail page to browse shared Team artifacts.
|
|
|
|
## 5. Choose a Template
|
|
|
|
- **Standard two-member Team**: a Leader coordinates one execution member for a focused task.
|
|
- **Delivery three-member Team**: implementation plus review for a small delivery.
|
|
- **Product discovery four-member Team**: product, design, and technical-feasibility exploration.
|
|
- **Software engineering eight-member Team**: product, design, frontend, backend, architecture, QA, and code review.
|
|
|
|
Templates are a starting point. Select the closest one, then add scope, constraints, and acceptance criteria in Team chat.
|