feat: remove git folder in workspace and add LEARNINGS.md with new monitoring guidelines and metadata

2026-04-07 14:50:11 +07:00
parent 19915856d8
commit 853d814a3f
2 changed files with 68 additions and 1 deletions
@@ -1 +0,0 @@
-.worktrees
@@ -323,6 +323,9 @@ When spawning ClawTeam agents, using `clawteam spawn subprocess openclaw` causes
 - Set task dependencies with `clawteam task update <team> <id> --add-blocked-by <dep-id>`
 - Monitor progress: `clawteam board attach <team>`

+### Metadata
+- Source: error
+- Tags: clawteam, spawn, subprocess, orchestration, critical
 ### Metadata
 - Source: error
 - Tags: clawteam, spawn, subprocess, orchestration, critical
@@ -331,3 +334,68 @@ When spawning ClawTeam agents, using `clawteam spawn subprocess openclaw` causes
 - First-Seen: 2026-04-06
 - Last-Seen: 2026-04-06

+---
+
+## [LRN-20260407-001] continuous_clawteam_monitoring_and_quality_control
+
+**Logged**: 2026-04-07T07:07:00Z
+**Priority**: critical
+**Status**: in_progress
+**Area**: orchestration/quality-control
+
+### Summary
+Continuous monitoring of ClawTeam progress and quality gates is mandatory to catch issues early and maintain consistent high-quality output.
+
+### Details
+User instruction: When ClawTeam is running, I must continuously monitor progress and check for specific quality control issues:
+
+**Task Status Issues**:
+- Blocked tasks that are not unblocked (stuck indefinitely)
+- Tasks stuck in `pending` without moving to `in_progress`
+- Tasks marked `in_progress` but not actually working (agents idle or unresponsive)
+- Tasks not blocked but still pending (missing dependencies or abandoned)
+
+**Agent Interaction & Review Issues**:
+- Agents not communicating with each other (lack of inbox usage)
+- Agents not doing self-review before reporting completion
+- Agents not doing peer review (skipping peer feedback stage)
+- Project manager not reviewing tasks (bypassing Tier 3 quality gate)
+
+This is a **proactive oversight** requirement, not a reactive one. We must regularly check (multiple times per day during active team operations) to catch these issues before they cascade. The goal is to ensure consistent quality and prevent substandard work from completing.
+
+### Suggested Action
+Establish a monitoring cadence and checklist for active ClawTeam projects:
+
+1. **Regular Check Schedule**
+   - Check team boards every 2-4 hours during active work periods
+   - More frequent (hourly) for tight deadlines / high-velocity teams
+   - Less frequent (twice daily) for low-velocity / planning phases
+
+2. **Monitoring Checklist**
+   - Review board: identify any `blocked` tasks not recently unblocked
+   - Check `pending` tasks: are old tasks stuck? Verify dependencies are set correctly
+   - Check `in_progress` tasks: are agents actually active? Use `clawteam context log` to see recent activity
+   - Verify inbox flow: are agents sending/receiving messages? Look for unanswered messages
+   - Review task transitions: ensure `completed` tasks went through `needs-self-review` → `needs-peer-review` → `needs-leader-review`
+   - Spot-check code: for tasks marked `completed`, verify worker did self-review, peer review occurred, and leader approval given
+
+3. **Automation/Aids**
+   - Create a script or alias to run quick checks: `clawteam board show <team>` + `clawteam task list <team> --status blocked` + `clawteam task list <team> --status in_progress`
+   - Set reminders during active development sprints
+   - Use `clawteam context conflicts` to detect worktree issues
+
+4. **Intervention Protocol**
+   - If an agent is idle (`in_progress` but no activity for >2h), send inbox message to check status
+   - If blocked task not unblocked, contact PM/leader to resolve
+   - If reviews skipped, request immediate self/peer review before allowing task to advance
+   - Document recurring issues in learnings to improve agent prompts/team setup
+
+### Metadata
+- Source: user_instruction
+- Tags: clawteam, monitoring, quality-gate, recurring-check, orchestration
+- Pattern-Key: orchestration.continuous_monitoring
+- Recurrence-Count: ongoing (recurring check)
+- First-Seen: 2026-04-07
+- Last-Seen: 2026-04-07
+
+---