kenaz 0.3.22 → 0.3.23

package/core/dev/pipeline/archived/TASK_099_backend_team_creation.yaml

@@ -1,258 +0,0 @@
-# TASK_099: Backend Team 建立 - 完整團隊結構、成員定義、權限矩陣、工作流程
-# Schema: dev/schemas/TASK.schema.json
-
-id: "TASK_099"
-title: "Backend Team 建立 - 完整團隊協作系統"
-description: |
-  建立完整的 Backend Team 結構，包含 7 個成員、權限矩陣、2 個工作流程。
-
-  **背景**：
-  .team 系統的 Product Manager Team 已完成 MVP，現在需要建立第一個「開發團隊」範例。
-  此任務將建立 Backend Team 作為多角色協作的完整展示。
-
-  **目標**：
-  建立可運作的後端開發團隊結構，展示成員定義、權限隔離、工作流程協調。
-
-  **交付物**：
-  1. TEAM.yaml - 團隊定義與協調規則
-  2. 7 個成員定義文件（members/ 目錄）
-  3. 權限矩陣（scope_matrix.yaml）
-  4. API 開發流程（api_development.yaml）
-  5. 資料庫遷移流程（database_migration.yaml）
-  6. 通訊框架結構（communication/ 目錄）
-
-priority: "P1"
-status: "pending"
-agent_type: "developer"
-source: "F-009 多角色團隊協作系統"
-feature_ids:
-  - "F-009"
-
-dependencies:
-  - "TASK_098"  # 可參考 Product Manager Team 的結構
-
-scope_paths:
-  - ".team/backend/"
-  - ".team/orchestrator/"
-
-requirements:
-  - "建立 .team/backend/TEAM.yaml（團隊定義、7 個成員、協調規則、通訊協議）"
-  - "建立 7 個成員定義文件：backend_lead、api_developer、database_specialist、doc_specialist、qa_engineer、security_specialist、performance_engineer"
-  - "建立 permissions/scope_matrix.yaml（後端專屬權限矩陣，每個成員的讀寫範圍）"
-  - "建立 permissions/lock_policy.yaml（文件鎖定政策，防止路徑衝突）"
-  - "建立 permissions/approval_flow.yaml（關鍵操作的審批流程）"
-  - "建立 workflows/api_development.yaml（至少 5 階段的 API 開發流程）"
-  - "建立 workflows/database_migration.yaml（資料庫遷移的完整流程）"
-  - "建立 communication/ 結構（message_queue.json、shared_context.json、handoff_protocol.yaml）"
-
-acceptance_criteria:
-  - ".team/backend/TEAM.yaml 正確定義了 7 個成員與協調規則，格式符合 Product Manager Team 規範"
-  - "所有 7 個成員定義文件存在於 .team/backend/members/ 目錄，每個文件包含角色、職責、權限範圍、技能、工作流程"
-  - "scope_matrix.yaml 清楚定義每個成員的讀寫範圍（如 API Developer 只能寫 backend/api/）"
-  - "api_development.yaml 包含至少 5 個階段：需求分析、API 設計、實現、文檔、測試與安全審計"
-  - "database_migration.yaml 包含完整流程：Schema 設計、Migration 撰寫、RLS 政策、測試驗證、部署"
-  - "權限設計確保不會有文件衝突（路徑獨佔，prevent race conditions）"
-  - "所有成員定義檔案包含 skill_path、職責描述、可讀/可寫路徑、approval_requirements"
-
-technical_notes:
-  - "成員定義參考 .team/product_manager/members/pm_lead.yaml 的格式與結構"
-  - "Backend 成員的權限範圍應限制在 backend/、supabase/、.security/ 等特定路徑"
-  - "使用 pathlib.Path.match() 進行路徑模式匹配（如 'backend/api/**/*.py'）"
-  - "文件鎖定使用 first-come-first-served 策略，鎖定記錄儲存在 .team/orchestrator/locks/"
-  - "API 開發流程應包含清晰的階段轉換條件與每個階段的進出標準"
-  - "Database Migration 流程應覆蓋 Schema 變更、數據遷移、RLS 政策、測試、部署 5 個節點"
-  - "通訊框架使用 JSON 格式儲存訊息隊列，支援 async 訊息傳遞"
-  - "成員協調使用 max_parallel_members 限制並行工作數量（建議 2-3 人）"
-
-estimated_hours: 8
-complexity: "complex"
-
-related_tasks:
-  - "TASK_098"  # Product Manager Team 完善
-  - "TASK_100"  # Frontend Team 建立
-  - "TASK_097"  # Team System Phase 1 (Reference)
-
-team_structure:
-  members:
-    - role: "backend_lead"
-      title: "後端技術主管"
-      count: 1
-      responsibilities: ["團隊協調、技術決策、Code Review 最終審批", "系統架構設計、關鍵技術選型", "跨部門協作協調"]
-
-    - role: "api_developer"
-      title: "API 開發工程師"
-      count: 2
-      responsibilities: ["API 端點設計實現", "業務邏輯開發", "API 文檔撰寫"]
-
-    - role: "database_specialist"
-      title: "資料庫專家"
-      count: 1
-      responsibilities: ["資料庫架構設計", "Migration 撰寫", "性能調優", "RLS 政策設計"]
-
-    - role: "doc_specialist"
-      title: "技術文檔專家"
-      count: 1
-      responsibilities: ["API 文檔撰寫", "架構文檔", "Deployment 指南", "故障排除文檔"]
-
-    - role: "qa_engineer"
-      title: "QA 工程師"
-      count: 1
-      responsibilities: ["單元測試撰寫", "集成測試", "性能測試", "缺陷追蹤與管理"]
-
-    - role: "security_specialist"
-      title: "安全專家"
-      count: 1
-      responsibilities: ["安全代碼審計", "RLS 政策審核", "API 安全加固", "漏洞修復"]
-
-    - role: "performance_engineer"
-      title: "性能工程師"
-      count: 1
-      responsibilities: ["性能基準測試", "瓶頸分析與優化", "數據庫查詢優化", "監控告警配置"]
-
-permission_matrix:
-  api_developer:
-    - "backend/api/**"           # API 實現代碼（可寫）
-    - "backend/models/**"         # 數據模型（可寫）
-    - "tests/api/**"              # API 測試（可寫）
-    - "docs/api/**"               # API 文檔（可讀）
-    - ".security/api/**"          # 安全政策（可讀）
-    read_only: ["backend/core/**", "supabase/migrations/**", "docs/deployment/**"]
-
-  database_specialist:
-    - "supabase/migrations/**"    # Migration 文件（可寫）
-    - "supabase/policies/**"      # RLS 政策（可寫）
-    - "backend/models/schema.py"  # 數據模型（可寫）
-    - "tests/database/**"         # 資料庫測試（可寫）
-    - "docs/database/**"          # 資料庫文檔（可寫）
-    read_only: ["backend/api/**", "backend/core/**"]
-
-  security_specialist:
-    - ".security/**"              # 安全政策（可寫）
-    - "backend/**"                # 後端代碼（可讀）
-    - "supabase/policies/**"      # RLS 政策（可讀）
-    approve_paths: ["backend/auth/**", "supabase/policies/**", ".security/**"]
-
-  performance_engineer:
-    - "backend/monitoring/**"     # 監控配置（可寫）
-    - "docs/performance/**"       # 性能文檔（可寫）
-    - "tests/performance/**"      # 性能測試（可寫）
-    read_only: ["backend/**", "supabase/**"]
-
-  backend_lead:
-    - ".team/backend/**"          # 團隊管理（可寫）
-    - "backend/**"                # 全部後端代碼（可寫）
-    read_only: []
-    approval_required: ["backend/core/**", ".security/**", "supabase/policies/**"]
-
-workflows:
-  - name: "api_development"
-    description: "API 開發工作流程（5 個階段）"
-    file: "workflows/api_development.yaml"
-    trigger: "new_api_requirement"
-    stages:
-      - name: "Requirements Analysis"
-        owner: "backend_lead"
-        duration: "4 hours"
-        output: "API 需求文檔"
-
-      - name: "API Design & Review"
-        owner: "backend_lead"
-        duration: "2 hours"
-        approvers: ["backend_lead", "database_specialist"]
-        output: "API 設計規格書"
-
-      - name: "Implementation"
-        owner: "api_developer"
-        duration: "8 hours"
-        requires: ["API Design & Review"]
-        output: "實現代碼、單元測試"
-
-      - name: "Testing & Documentation"
-        owner: ["qa_engineer", "doc_specialist"]
-        duration: "4 hours"
-        requires: ["Implementation"]
-        output: "測試報告、API 文檔"
-
-      - name: "Security Audit & Deployment"
-        owner: "security_specialist"
-        duration: "2 hours"
-        approvers: ["security_specialist", "backend_lead"]
-        output: "安全審計報告、部署清單"
-
-  - name: "database_migration"
-    description: "資料庫遷移工作流程（5 個節點）"
-    file: "workflows/database_migration.yaml"
-    trigger: "schema_change_required"
-    stages:
-      - name: "Schema Design & Review"
-        owner: "database_specialist"
-        duration: "3 hours"
-        approvers: ["backend_lead", "performance_engineer"]
-        output: "Schema 設計文檔"
-
-      - name: "Migration SQL Writing"
-        owner: "database_specialist"
-        duration: "3 hours"
-        requires: ["Schema Design & Review"]
-        output: "Migration 文件、Rollback 腳本"
-
-      - name: "RLS Policy Definition"
-        owner: ["security_specialist", "database_specialist"]
-        duration: "2 hours"
-        requires: ["Migration SQL Writing"]
-        output: "RLS 政策代碼"
-
-      - name: "Testing & Performance Validation"
-        owner: ["qa_engineer", "performance_engineer"]
-        duration: "4 hours"
-        requires: ["RLS Policy Definition"]
-        output: "測試報告、性能基準"
-
-      - name: "Deployment & Verification"
-        owner: "backend_lead"
-        duration: "2 hours"
-        approvers: ["backend_lead", "database_specialist", "security_specialist"]
-        output: "部署日誌、驗證報告"
-
-conflict_resolution:
-  strategy: "path_based_locking"
-  owner_fallback: "backend_lead"
-  escalation_path: "Product Manager Lead"
-  max_lock_wait_time: "30 minutes"
-
-coordination:
-  max_parallel_members: 2        # 最多同時 2 個成員並行工作（防止路徑衝突）
-  conflict_resolution: "leader"  # 衝突由 backend_lead 決策
-  approval_threshold: 2          # 關鍵操作需至少 2 人同意
-  sync_frequency: "2 hours"      # 每 2 小時同步一次狀態
-
-metadata:
-  created_at: "2026-02-06T17:30:00+08:00"
-  created_by: "Product Manager Agent (Lead)"
-  version: "1.0.0"
-  feature: "F-009 多角色團隊協作系統"
-  research_references:
-    - ".team/product_manager/TEAM.yaml"
-    - "CLAUDE.md - Agent 系統文件"
-    - ".failure/FAIL-003 - 多 Agent 協作經驗教訓"
-
-implementation_checklist:
-  - "□ 建立 .team/backend/ 目錄結構"
-  - "□ 複製 .team/product_manager/TEAM.yaml 並修改為 backend 版本"
-  - "□ 建立 7 個 members/*.yaml 檔案（backend_lead, api_developer x2, database_specialist, doc_specialist, qa_engineer, security_specialist, performance_engineer）"
-  - "□ 設計 permissions/scope_matrix.yaml（路徑隔離矩陣）"
-  - "□ 設計 permissions/lock_policy.yaml（鎖定政策）"
-  - "□ 設計 permissions/approval_flow.yaml（審批流程）"
-  - "□ 實現 workflows/api_development.yaml（5 階段）"
-  - "□ 實現 workflows/database_migration.yaml（5 節點）"
-  - "□ 建立 communication/ 結構（message_queue.json, shared_context.json, handoff_protocol.yaml）"
-  - "□ 編寫單元測試驗證權限矩陣"
-  - "□ 建立集成測試驗證工作流程"
-  - "□ 文檔生成：TEAM.md（概述）、MEMBER_ROLES.md（成員指南）"
-
-success_metrics:
-  - "所有團隊文件構建完成，無語法錯誤"
-  - "路徑隔離測試成功（7 個成員各自在自己的路徑上）"
-  - "工作流程轉換流暢（5 階段 API 開發可完整執行）"
-  - "權限檢查機制有效（非授權成員無法寫入受限路徑）"
-  - "團隊文件被 TASK_100（Frontend Team）順利參考"

package/core/dev/pipeline/archived/TASK_100_frontend_team_creation.yaml

@@ -1,61 +0,0 @@
-# TASK_100: Frontend Team 建立
-# Schema: dev/schemas/TASK.schema.json
-
-id: "TASK_100"
-title: "Frontend Team 建立"
-description: |
-  建立完整的 Frontend Team 結構，包含團隊定義、6 個成員、權限矩陣與工作流程。
-
-  **背景**：
-  .team 系統需要建立前端開發團隊，展示 React/TypeScript 開發的多角色協作。
-
-  **目標**：
-  讓 Frontend Team 成為完整可運作的前端開發團隊。
-
-priority: "P1"
-status: "pending"
-agent_type: "developer"
-source: "F-009"
-feature_ids:
-  - "F-009"
-
-dependencies:
-  - "TASK_098"  # 可參考 Product Manager Team 的結構
-
-scope_paths:
-  - ".team/frontend/"
-
-requirements:
-  - "建立 .team/frontend/TEAM.yaml（團隊定義）"
-  - "建立 6 個成員定義文件（frontend_lead, ui_developer, ux_specialist, doc_specialist, qa_engineer, accessibility_expert）"
-  - "建立 permissions/scope_matrix.yaml（前端專屬權限矩陣）"
-  - "建立 permissions/lock_policy.yaml（鎖定政策）"
-  - "建立 workflows/component_development.yaml（組件開發流程）"
-  - "建立 workflows/ux_optimization.yaml（UX 優化流程）"
-  - "建立 communication/ 目錄結構"
-
-acceptance_criteria:
-  - ".team/frontend/TEAM.yaml 定義了 6 個成員與協作規則"
-  - "所有 6 個成員定義文件存在於 members/ 目錄"
-  - "scope_matrix.yaml 定義了每個成員的權限範圍（如 UI Developer 只能寫 dashboard/src/components/）"
-  - "component_development.yaml 包含組件開發的完整流程（設計稿 → 組件實作 → 樣式 → 測試 → 文檔）"
-  - "ux_optimization.yaml 包含 UX 優化流程（用戶研究 → 問題識別 → 方案設計 → A/B 測試）"
-  - "Accessibility Expert 能審查無障礙合規性"
-
-technical_notes:
-  - "參考 .team/product_manager/ 的結構設計"
-  - "Frontend 成員的權限範圍應該限制在 dashboard/src/、dashboard/docs/ 等路徑"
-  - "UI Developer 與 UX Specialist 的權限應有所區分（UI 寫代碼，UX 寫設計文檔）"
-  - "Accessibility Expert 應能訪問所有前端代碼但只能寫入 .accessibility/audit/"
-
-estimated_hours: 5
-complexity: "medium"
-
-related_tasks:
-  - "TASK_098"  # Product Manager Team 完善
-  - "TASK_099"  # Backend Team
-
-metadata:
-  created_at: "2026-02-06T17:30:00+08:00"
-  created_by: "Product Manager Agent (Lead)"
-  feature: "F-009 多角色團隊協作系統"