claude-code-workflow 6.2.3 → 6.2.5

package/.claude/workflows/cli-templates/protocols/analysis-protocol.md

@@ -1,112 +0,0 @@
-# Analysis Mode Protocol
-
-## Mode Definition
-
-**Mode**: `analysis` (READ-ONLY)
-**Tools**: Gemini, Qwen (default mode)
-
-## Operation Boundaries
-
-### ALLOWED Operations
-- **READ**: All CONTEXT files and analyze content
-- **ANALYZE**: Code patterns, architecture, dependencies
-- **GENERATE**: Text output, insights, recommendations
-- **DOCUMENT**: Analysis results in output response only
-
-### FORBIDDEN Operations
-- **NO FILE CREATION**: Cannot create any files on disk
-- **NO FILE MODIFICATION**: Cannot modify existing files
-- **NO FILE DELETION**: Cannot delete any files
-- **NO DIRECTORY OPERATIONS**: Cannot create/modify directories
-
-**CRITICAL**: Absolutely NO file system operations - OUTPUT ONLY
-
-## Execution Flow
-
-1. **Parse** all 6 fields (PURPOSE, TASK, MODE, CONTEXT, EXPECTED, RULES)
-2. **Read** and analyze CONTEXT files thoroughly
-3. **Identify** patterns, issues, and dependencies
-4. **Generate** insights and recommendations
-5. **Output** structured analysis (text response only)
-6. **Validate** EXPECTED deliverables met
-
-## Core Requirements
-
-**ALWAYS**:
-- Analyze ALL CONTEXT files completely
-- Apply RULES (templates + constraints) exactly
-- Provide code evidence with `file:line` references
-- List all related/analyzed files at output beginning
-- Match EXPECTED deliverables precisely
-
-**NEVER**:
-- Assume behavior without code verification
-- Ignore CONTEXT file patterns
-- Skip RULES or templates
-- Make unsubstantiated claims
-- Create/modify/delete any files
-
-## RULES Processing
-
-- Parse RULES field to extract template content and constraints
-- Recognize `|` as separator: `template content | additional constraints`
-- Apply ALL template guidelines as mandatory
-- Treat rule violations as task failures
-
-## Error Handling
-
-**File Not Found**: Report missing files, continue with available, note in output
-**Invalid CONTEXT Pattern**: Report invalid pattern, request correction, do not guess
-
-## Quality Standards
-
-- **Thoroughness**: Analyze ALL files, check cross-file patterns, quantify metrics
-- **Evidence-Based**: Quote code with `file:line`, link patterns, support claims with examples
-- **Actionable**: Clear recommendations, prioritized by impact, incremental changes
-
----
-
-## Output Format
-
-### Format Priority
-
-**If template defines output format** → Follow template format EXACTLY
-
-**If template has no format** → Use default format below
-
-### Default Analysis Output
-
-```markdown
-# Analysis: [TASK Title]
-
-## Related Files
-- `path/to/file1.ext` - [Brief description of relevance]
-- `path/to/file2.ext` - [Brief description of relevance]
-
-## Summary
-[2-3 sentence overview]
-
-## Key Findings
-1. [Finding] - path/to/file:123
-2. [Finding] - path/to/file:456
-
-## Detailed Analysis
-[Evidence-based analysis with code quotes]
-
-## Recommendations
-1. [Actionable recommendation]
-2. [Actionable recommendation]
-```
-
-### Code References
-
-**Format**: `path/to/file:line_number`
-**Example**: `src/auth/jwt.ts:45` - Authentication uses deprecated algorithm
-
-### Quality Checklist
-
-- [ ] All CONTEXT files analyzed
-- [ ] Code evidence with `file:line` references
-- [ ] Specific, actionable recommendations
-- [ ] No unsubstantiated claims
-- [ ] EXPECTED deliverables met

package/.claude/workflows/cli-templates/protocols/write-protocol.md

@@ -1,201 +0,0 @@
-# Write Mode Protocol
-
-## Mode Definition
-
-**Mode**: `write` (FILE OPERATIONS) / `auto` (FULL OPERATIONS)
-**Tools**: Codex (auto), Gemini/Qwen (write)
-
-## Operation Boundaries
-
-### MODE: write
-- **READ**: All CONTEXT files and analyze content
-- **CREATE**: New files (documentation, code, configuration)
-- **MODIFY**: Existing files (update content, refactor code)
-- **DELETE**: Files when explicitly required
-
-**Restrictions**: Follow project conventions, cannot break existing functionality
-
-### MODE: auto (Codex only)
-- All `write` mode operations
-- Run tests and builds
-- Commit code incrementally
-- Full autonomous development
-
-**Constraint**: Must test every change
-
-## Execution Flow
-
-### MODE: write
-1. **Parse** all 6 fields (PURPOSE, TASK, MODE, CONTEXT, EXPECTED, RULES)
-2. **Read** CONTEXT files, find 3+ similar patterns
-3. **Plan** implementation following RULES
-4. **Execute** requested file operations
-5. **Validate** changes
-6. **Report** file changes
-
-### MODE: auto
-1. **Parse** all 6 fields
-2. **Analyze** CONTEXT files - find 3+ similar patterns
-3. **Plan** implementation following RULES
-4. **Generate** code with tests
-5. **Run** tests continuously
-6. **Commit** working code incrementally
-7. **Validate** EXPECTED deliverables
-8. **Report** results
-
-## Core Requirements
-
-**ALWAYS**:
-- Study CONTEXT files - find 3+ similar patterns before implementing
-- Apply RULES exactly
-- Test continuously (auto mode)
-- Commit incrementally (auto mode)
-- Match project style exactly
-- List all created/modified files at output beginning
-
-**NEVER**:
-- Make assumptions without code verification
-- Ignore existing patterns
-- Skip tests (auto mode)
-- Use clever tricks over boring solutions
-- Break backward compatibility
-- Exceed 3 failed attempts without stopping
-
-## Multi-Task Execution (Resume)
-
-**First subtask**: Standard execution flow
-**Subsequent subtasks** (via `resume`):
-- Recall context from previous subtasks
-- Build on previous work
-- Maintain consistency
-- Test integration
-- Report context for next subtask
-
-## Error Handling
-
-**Three-Attempt Rule**: On 3rd failure, stop and report what attempted, what failed, root cause
-
-| Error Type | Response |
-|------------|----------|
-| Syntax/Type | Review → Fix → Re-run tests |
-| Runtime | Analyze stack → Add handling → Test |
-| Test Failure | Debug → Review setup → Fix |
-| Build Failure | Check messages → Fix incrementally |
-
----
-
-## Output Format
-
-### Format Priority
-
-**If template defines output format** → Follow template format EXACTLY
-
-**If template has no format** → Use default format below
-
-### Single Task Implementation
-
-```markdown
-# Implementation: [TASK Title]
-
-## Changes
-- Created: `path/to/file1.ext` (X lines)
-- Modified: `path/to/file2.ext` (+Y/-Z lines)
-- Deleted: `path/to/file3.ext`
-
-## Summary
-[2-3 sentence overview]
-
-## Key Decisions
-1. [Decision] - Rationale and reference to similar pattern
-2. [Decision] - path/to/reference:line
-
-## Implementation Details
-[Evidence-based description with code references]
-
-## Testing
-- Tests written: X new tests
-- Tests passing: Y/Z tests
-
-## Validation
-✅ Tests: X passing
-✅ Build: Success
-
-## Next Steps
-[Recommendations if any]
-```
-
-### Multi-Task (First Subtask)
-
-```markdown
-# Subtask 1/N: [TASK Title]
-
-## Changes
-[List of file changes]
-
-## Implementation
-[Details with code references]
-
-## Testing
-✅ Tests: X passing
-
-## Context for Next Subtask
-- Key decisions: [established patterns]
-- Files created: [paths and purposes]
-- Integration points: [where next subtask should connect]
-```
-
-### Multi-Task (Subsequent Subtasks)
-
-```markdown
-# Subtask N/M: [TASK Title]
-
-## Changes
-[List of file changes]
-
-## Integration Notes
-✅ Compatible with previous subtask
-✅ Maintains established patterns
-
-## Implementation
-[Details with code references]
-
-## Testing
-✅ Tests: X passing
-
-## Context for Next Subtask
-[If not final, provide context]
-```
-
-### Partial Completion
-
-```markdown
-# Task Status: Partially Completed
-
-## Completed
-- [What worked]
-- Files: `path/to/completed.ext`
-
-## Blocked
-- **Issue**: [What failed]
-- **Root Cause**: [Analysis]
-- **Attempted**: [Solutions tried - attempt X of 3]
-
-## Required
-[What's needed to proceed]
-
-## Recommendation
-[Suggested next steps]
-```
-
-### Code References
-
-**Format**: `path/to/file:line_number`
-**Example**: `src/auth/jwt.ts:45` - Implemented following pattern from `src/auth/session.ts:78`
-
-### Quality Checklist
-
-- [ ] All tests pass
-- [ ] Build succeeds
-- [ ] All EXPECTED deliverables met
-- [ ] Code follows existing patterns
-- [ ] File changes listed at beginning

package/.claude/workflows/cli-templates/schemas/conflict-resolution-schema.json

@@ -1,137 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Conflict Resolution Schema",
-  "description": "Simplified schema for conflict detection and resolution",
-
-  "type": "object",
-  "required": ["conflicts", "summary"],
-  "properties": {
-    "conflicts": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "required": ["id", "brief", "severity", "category", "strategies"],
-        "properties": {
-          "id": {
-            "type": "string",
-            "pattern": "^CON-\\d{3}$",
-            "description": "Conflict ID (CON-001, CON-002, ...)"
-          },
-          "brief": {
-            "type": "string",
-            "description": "一句话冲突摘要（中文）"
-          },
-          "severity": {
-            "enum": ["Critical", "High", "Medium"],
-            "description": "冲突严重程度"
-          },
-          "category": {
-            "enum": ["Architecture", "API", "Data", "Dependency", "ModuleOverlap"],
-            "description": "冲突类型"
-          },
-          "affected_files": {
-            "type": "array",
-            "items": { "type": "string" },
-            "description": "受影响的文件路径"
-          },
-          "description": {
-            "type": "string",
-            "description": "详细冲突描述"
-          },
-          "clarification_questions": {
-            "type": "array",
-            "items": { "type": "string" },
-            "description": "需要用户澄清的问题（可选）"
-          },
-          "strategies": {
-            "type": "array",
-            "minItems": 2,
-            "maxItems": 4,
-            "items": {
-              "type": "object",
-              "required": ["name", "approach", "complexity", "risk"],
-              "properties": {
-                "name": {
-                  "type": "string",
-                  "description": "策略名称（中文）"
-                },
-                "approach": {
-                  "type": "string",
-                  "description": "实现方法简述"
-                },
-                "complexity": {
-                  "enum": ["Low", "Medium", "High"]
-                },
-                "risk": {
-                  "enum": ["Low", "Medium", "High"]
-                },
-                "constraints": {
-                  "type": "array",
-                  "items": { "type": "string" },
-                  "description": "实施此策略的约束条件（传递给 task-generate）"
-                }
-              }
-            }
-          },
-          "recommended": {
-            "type": "integer",
-            "minimum": 0,
-            "description": "推荐策略索引（0-based）"
-          }
-        }
-      }
-    },
-    "summary": {
-      "type": "object",
-      "required": ["total"],
-      "properties": {
-        "total": { "type": "integer" },
-        "critical": { "type": "integer" },
-        "high": { "type": "integer" },
-        "medium": { "type": "integer" }
-      }
-    }
-  },
-
-  "examples": [
-    {
-      "conflicts": [
-        {
-          "id": "CON-001",
-          "brief": "新认证模块与现有 AuthManager 功能重叠",
-          "severity": "High",
-          "category": "ModuleOverlap",
-          "affected_files": ["src/auth/AuthManager.ts"],
-          "description": "计划新增的 UserAuthService 与现有 AuthManager 在登录和 Token 验证场景存在重叠",
-          "clarification_questions": [
-            "新模块的核心职责边界是什么？",
-            "哪些场景应该由新模块独立处理？"
-          ],
-          "strategies": [
-            {
-              "name": "扩展现有模块",
-              "approach": "在 AuthManager 中添加新功能",
-              "complexity": "Low",
-              "risk": "Low",
-              "constraints": ["保持 AuthManager 作为唯一认证入口", "新增 MFA 方法"]
-            },
-            {
-              "name": "职责拆分",
-              "approach": "AuthManager 负责基础认证，新模块负责高级认证",
-              "complexity": "Medium",
-              "risk": "Medium",
-              "constraints": ["定义清晰的接口边界", "基础认证 = 密码+token", "高级认证 = MFA+OAuth"]
-            }
-          ],
-          "recommended": 0
-        }
-      ],
-      "summary": {
-        "total": 1,
-        "critical": 0,
-        "high": 1,
-        "medium": 0
-      }
-    }
-  ]
-}

package/.claude/workflows/cli-templates/schemas/debug-log-json-schema.json

@@ -1,127 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Debug Log Entry Schema",
-  "description": "NDJSON log entry for hypothesis-driven debugging workflow",
-  "type": "object",
-  "required": [
-    "sessionId",
-    "runId",
-    "hypothesisId",
-    "location",
-    "message",
-    "data",
-    "timestamp"
-  ],
-  "properties": {
-    "sessionId": {
-      "type": "string",
-      "pattern": "^DBG-[a-z0-9-]+-\\d{4}-\\d{2}-\\d{2}$",
-      "description": "Debug session identifier (e.g., 'DBG-stack-length-not-found-2025-12-18')"
-    },
-    "runId": {
-      "type": "string",
-      "pattern": "^run-\\d+$",
-      "description": "Reproduction run number (e.g., 'run-1', 'run-2')"
-    },
-    "hypothesisId": {
-      "type": "string",
-      "pattern": "^H\\d+$",
-      "description": "Hypothesis identifier being tested (e.g., 'H1', 'H2')"
-    },
-    "location": {
-      "type": "string",
-      "description": "Code location in format 'file:function:line' or 'file:line'"
-    },
-    "message": {
-      "type": "string",
-      "description": "Human-readable description of what's being logged"
-    },
-    "data": {
-      "type": "object",
-      "additionalProperties": true,
-      "description": "Captured values for hypothesis validation",
-      "properties": {
-        "keys_sample": {
-          "type": "array",
-          "items": {"type": "string"},
-          "description": "Sample of dictionary/object keys (first 30)"
-        },
-        "value": {
-          "description": "Captured value (any type)"
-        },
-        "expected_value": {
-          "description": "Expected value for comparison"
-        },
-        "actual_type": {
-          "type": "string",
-          "description": "Actual type of captured value"
-        },
-        "count": {
-          "type": "integer",
-          "description": "Count of items (for arrays/collections)"
-        },
-        "is_null": {
-          "type": "boolean",
-          "description": "Whether value is null/None"
-        },
-        "is_empty": {
-          "type": "boolean",
-          "description": "Whether collection is empty"
-        },
-        "comparison_result": {
-          "type": "string",
-          "enum": ["match", "mismatch", "partial_match"],
-          "description": "Result of value comparison"
-        }
-      }
-    },
-    "timestamp": {
-      "type": "integer",
-      "description": "Unix timestamp in milliseconds"
-    },
-    "severity": {
-      "type": "string",
-      "enum": ["debug", "info", "warning", "error"],
-      "default": "info",
-      "description": "Log severity level"
-    },
-    "stack_trace": {
-      "type": "string",
-      "description": "Stack trace if capturing exception context"
-    },
-    "parent_entry_id": {
-      "type": "string",
-      "description": "Reference to parent log entry for nested contexts"
-    }
-  },
-  "examples": [
-    {
-      "sessionId": "DBG-stack-length-not-found-2025-12-18",
-      "runId": "run-1",
-      "hypothesisId": "H1",
-      "location": "rmxprt_api/core/rmxprt_parameter.py:sync_from_machine:642",
-      "message": "Inspect stator keys from machine.to_dict and compare Stack Length vs Length",
-      "data": {
-        "keys_sample": ["Length", "Outer Diameter", "Inner Diameter", "Slot"],
-        "stack_length_value": "未找到",
-        "length_value": "120mm",
-        "comparison_result": "mismatch"
-      },
-      "timestamp": 1734523456789
-    },
-    {
-      "sessionId": "DBG-registered-zero-2025-12-18",
-      "runId": "run-1",
-      "hypothesisId": "H2",
-      "location": "rmxprt_api/utils/param_core.py:update_variables_from_result_model:670",
-      "message": "Check result parameters count and sample keys",
-      "data": {
-        "count": 0,
-        "is_empty": true,
-        "sections_parsed": ["Stator", "Rotor", "General"],
-        "expected_count": 145
-      },
-      "timestamp": 1734523457123
-    }
-  ]
-}