feat: add more skills (from everything-claude-code), config (rules, agents, tools, learning), add new 2 tempalte for dev-team and qc-team
This commit is contained in:
@@ -174,6 +174,72 @@ User explicitly stated: "với mọi dự án thì tôi đều muốn mọi th
|
||||
- First-Seen: 2026-03-31
|
||||
- Last-Seen: 2026-03-31
|
||||
|
||||
---
|
||||
## New Learnings — 2026-04-06 (ClawTeam Templates & Dev Team Expansion)
|
||||
|
||||
### [LRN-20260406-001] use_clawteam_templates_for_team_creation
|
||||
|
||||
**Logged**: 2026-04-06T07:25:00Z
|
||||
**Priority**: high
|
||||
**Status**: resolved
|
||||
**Area**: orchestration
|
||||
|
||||
### Summary
|
||||
When a requested team type doesn't exist, first check `~/.clawteam/templates/` for a matching template before creating a team from scratch.
|
||||
|
||||
### Details
|
||||
User instruction: If dev-team (or any team type) doesn't exist, look in `~/.clawteam/templates/` directory first. Templates provide pre-configured roles, tasks, and worker instructions. Available templates:
|
||||
- `dev-team.toml` — Tech Lead + Full-stack + Frontend + Backend + UX/UI
|
||||
- `qc-team.toml` — QC Lead + Code Reviewer + Test Engineer + Acceptance Auditor
|
||||
|
||||
Before spawning any team, run `ls ~/.clawteam/templates/` to see what's available. If template exists, use it as the base configuration.
|
||||
|
||||
### Suggested Action
|
||||
- Always check `~/.clawteam/templates/` when user requests team creation
|
||||
- If template exists, use it (modify if needed)
|
||||
- If no template exists, create one from scratch and save to templates for future reuse
|
||||
|
||||
### Metadata
|
||||
- Source: user_instruction
|
||||
- Related Files: ~/.clawteam/templates/dev-team.toml, ~/.clawteam/templates/qc-team.toml
|
||||
- Tags: clawteam, templates, team-creation
|
||||
- Pattern-Key: orchestration.use_templates_for_teams
|
||||
- Recurrence-Count: 1
|
||||
- First-Seen: 2026-04-06
|
||||
|
||||
---
|
||||
|
||||
### [LRN-20260406-002] dev_team_includes_qc_and_devops
|
||||
|
||||
**Logged**: 2026-04-06T07:30:00Z
|
||||
**Priority**: high
|
||||
**Status**: resolved
|
||||
**Area**: orchestration
|
||||
|
||||
### Summary
|
||||
Dev team must include QC (Quality Control) and DevOps roles. Updated dev-team.toml template to add `qc-lead`, `qa-engineer`, and `devops-engineer` agents.
|
||||
|
||||
### Details
|
||||
User explicitly requested adding 1 QC and 1 DevOps to the dev-team template. Updated `~/.clawteam/templates/dev-team.toml` with:
|
||||
- `qc-lead` — Code quality gate, review coordination, acceptance criteria
|
||||
- `qa-engineer` — Test coverage, TDD compliance, edge case validation, regression tests
|
||||
- `devops-engineer` — CI/CD, Docker, deployment, monitoring, infrastructure
|
||||
|
||||
Also added initial tasks for QC (quality criteria definition) and DevOps (CI pipeline setup).
|
||||
|
||||
### Suggested Action
|
||||
- When spawning dev teams, always include QC and DevOps members
|
||||
- QC runs after feature implementation (dependent tasks)
|
||||
- DevOps works in parallel for CI/CD setup early
|
||||
|
||||
### Metadata
|
||||
- Source: user_instruction
|
||||
- Related Files: ~/.clawteam/templates/dev-team.toml
|
||||
- Tags: clawteam, team-structure, qc, devops
|
||||
- Pattern-Key: orchestration.dev_team_with_qc_devops
|
||||
- Recurrence-Count: 1
|
||||
- First-Seen: 2026-04-06
|
||||
|
||||
---
|
||||
## New Learnings — 2026-04-03 (ClawTeam Deep Dive)
|
||||
|
||||
@@ -199,4 +265,32 @@ NEVER use sessions_spawn for multi-agent coordination. ALWAYS use clawteam CLI.
|
||||
- Recurrence-Count: 3
|
||||
- First-Seen: 2026-04-03
|
||||
|
||||
---
|
||||
---
|
||||
### [LRN-20260406-003] strict_quality_gate_and_template_usage
|
||||
|
||||
**Logged**: 2026-04-06T08:04:00Z
|
||||
**Priority**: critical
|
||||
**Status**: resolved
|
||||
**Area**: orchestration
|
||||
|
||||
### Summary
|
||||
PM must enforce strict quality standards using templates and zero-tolerance policy; all teams must use templates from ~/.clawteam/templates/.
|
||||
|
||||
### Details
|
||||
User explicitly required: khi review code thì phải cực kỳ khắt khe, phải đạt mọi tiêu chuẩn cao, không để tasks/projects không đạt chất lượng. Added comprehensive strict quality checklist to RULES.md and enhanced AGENTS.md with enforcement note. Also ensured dev and QC team templates use PM role and include QC/DevOps.
|
||||
|
||||
### Suggested Action
|
||||
- PMs must verify all tasks independently (read diff, run tests, check coverage)
|
||||
- Use the strict checklist; reject any non-compliance
|
||||
- Always check templates directory when creating teams
|
||||
- No task may complete unless ALL criteria passed
|
||||
|
||||
### Metadata
|
||||
- Source: user_instruction
|
||||
- Related Files: RULES.md, AGENTS.md, ~/.clawteam/templates/dev-team.toml, ~/.clawteam/templates/qc-team.toml
|
||||
- Tags: quality, strict, template, review
|
||||
- Pattern-Key: orchestration.strict_quality_gate
|
||||
- Recurrence-Count: 1
|
||||
- First-Seen: 2026-04-06
|
||||
- Last-Seen: 2026-04-06
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user