Add quality standards and team command design patterns documentation

- Introduced a new quality standards document outlining assessment criteria for team command .md files, including completeness, pattern compliance, integration, and consistency dimensions.
- Established quality gates and issue classification for errors, warnings, and informational notes.
- Created a comprehensive team command design patterns document detailing infrastructure and collaboration patterns, including message bus integration, YAML front matter requirements, task lifecycle, five-phase execution structure, and error handling.
- Included a pattern selection guide for collaboration scenarios to enhance team interaction models.

.claude/commands/issue/execute.md

@@ -337,7 +337,7 @@ Execute each task in order (T1 → T2 → T3 → ...):
 For each task:
 - Follow task.implementation steps
 - Run task.test commands
-- Verify task.acceptance criteria
+- Verify task.convergence criteria
 - Do NOT commit after each task
 
 ### Step 3: Commit Solution (Once)
@@ -380,7 +380,7 @@ On success, run:
     "tests_passed": true,
     "verification": {
       "all_tests_passed": true,
-      "acceptance_criteria_met": true,
+      "convergence_criteria_met": true,
       "regression_checked": true
     },
     "summary": "<brief description of accomplishment>"

.claude/commands/issue/from-brainstorm.md

@@ -105,12 +105,12 @@ interface Task {
   description: string;
 
   implementation: string[];      // Step-by-step guide
-  acceptance: {
+  convergence: {
     criteria: string[];          // What defines success
     verification: string[];      // How to verify
   };
 
-  priority: number;              // 1-5
+  priority: string;              // "critical"|"high"|"medium"|"low"
   depends_on: string[];          // Task dependencies
 }
 ```
@@ -146,7 +146,7 @@ Phase 5: Generate Solution Tasks
    ├─ T1: Research & Validate (if main_challenges exist)
    ├─ T2: Design & Specification (if key_strengths exist)
    ├─ T3+: Implementation tasks (from idea.next_steps)
-   └─ Each task includes: implementation steps + acceptance criteria
+   └─ Each task includes: implementation steps + convergence criteria
 
 Phase 6: Bind Solution
    ├─ Write solution to .workflow/issues/solutions/{issue-id}.jsonl
@@ -214,7 +214,7 @@ Phase 7: Next Steps
 - **Title**: `idea.title`
 - **Scope**: implementation
 - **Action**: Implement
-- **Generic implementation + acceptance criteria**
+- **Generic implementation + convergence criteria**
 
 ## Priority Calculation
 

.claude/commands/issue/plan.md

@@ -191,7 +191,7 @@ ${issueList}
 - Solution ID format: SOL-{issue-id}-{uid} (uid: 4 random alphanumeric chars, e.g., a7x9)
 - Single solution per issue → auto-bind via ccw issue bind
 - Multiple solutions → register only, return pending_selection
-- Tasks must have quantified acceptance.criteria
+- Tasks must have quantified convergence.criteria
 
 ### Return Summary
 {"bound":[{"issue_id":"...","solution_id":"...","task_count":N}],"pending_selection":[{"issue_id":"...","solutions":[{"id":"...","description":"...","task_count":N}]}]}
@@ -323,8 +323,8 @@ Before completing, verify:
 - [ ] All input issues have solutions in `solutions/{issue-id}.jsonl`
 - [ ] Single solution issues are auto-bound (`bound_solution_id` set)
 - [ ] Multi-solution issues returned in `pending_selection` for user choice
-- [ ] Each solution has executable tasks with `modification_points`
-- [ ] Task acceptance criteria are quantified (not vague)
+- [ ] Each solution has executable tasks with `files`
+- [ ] Task convergence criteria are quantified (not vague)
 - [ ] Conflicts detected and reported (if multiple issues touch same files)
 - [ ] Issue status updated to `planned` after binding
 

.claude/commands/issue/queue.md

@@ -88,7 +88,7 @@ ccw issue queue delete <queue-id>     Delete queue from history
 Phase 1: Solution Loading & Distribution
    ├─ Load issues.jsonl, filter by status='planned' + bound_solution_id
    ├─ Read solutions/{issue-id}.jsonl, find bound solution
-   ├─ Extract files_touched from task modification_points
+   ├─ Extract files_touched from task files[] or modification_points (legacy)
    ├─ Build solution objects array
    └─ If --queues > 1: Partition solutions into N groups (minimize cross-group file conflicts)