claude-code-workflow 6.3.53 → 7.0.0

package/.codex/agents/ccw-loop-b-complete.md

@@ -1,227 +0,0 @@
-# Worker: Complete (CCW Loop-B)
-
-Finalize session: summary generation, cleanup, commit preparation.
-
-## Responsibilities
-
-1. **Generate summary**
-   - Consolidate all progress
-   - Document achievements
-   - List changes
-
-2. **Review completeness**
-   - Check pending tasks
-   - Verify quality gates
-   - Ensure documentation
-
-3. **Prepare commit**
-   - Format commit message
-   - List changed files
-   - Suggest commit strategy
-
-4. **Cleanup**
-   - Archive progress files
-   - Update loop state
-   - Mark session complete
-
-## Input
-
-```
-LOOP CONTEXT:
-- All worker outputs
-- Progress files
-- Current state
-
-PROJECT CONTEXT:
-- Git repository state
-- Recent commits
-- Project conventions
-```
-
-## Execution Steps
-
-1. **Read all progress**
-   - Load worker outputs from `.workflow/.loop/{loopId}.workers/`
-   - Read progress files from `.workflow/.loop/{loopId}.progress/`
-   - Consolidate findings
-
-2. **Verify completeness**
-   - Check all tasks completed
-   - Verify tests passed
-   - Confirm quality gates
-
-3. **Generate summary**
-   - Create achievement list
-   - Document changes
-   - Highlight key points
-
-4. **Prepare commit**
-   - Write commit message
-   - List files changed
-   - Suggest branch strategy
-
-5. **Cleanup state**
-   - Archive progress
-   - Update loop status
-   - Output completion
-
-## Output Format
-
-```
-WORKER_RESULT:
-- action: complete
-- status: success | partial | failed
-- summary: "Completed X tasks, implemented Y features, all tests pass"
-- files_changed: []
-- next_suggestion: null
-- loop_back_to: null
-
-SESSION_SUMMARY:
-  loop_id: "loop-b-20260122-abc123"
-  task: "Implement user authentication"
-  duration: "45 minutes"
-  iterations: 5
-  
-  achievements:
-    - Implemented login/logout functions
-    - Added JWT token handling
-    - Wrote 15 unit tests (100% coverage)
-    - Fixed 2 security vulnerabilities
-  
-  files_changed:
-    - src/auth.ts (created, +180 lines)
-    - src/utils.ts (modified, +45/-10 lines)
-    - tests/auth.test.ts (created, +150 lines)
-  
-  test_results:
-    total: 113
-    passed: 113
-    failed: 0
-    coverage: "95%"
-  
-  quality_checks:
-    lint: ✓ Pass
-    types: ✓ Pass
-    security: ✓ Pass
-
-COMMIT_SUGGESTION:
-  message: |
-    feat: Implement user authentication
-    
-    - Add login/logout functions with session management
-    - Implement JWT token encode/decode utilities
-    - Create comprehensive test suite (15 tests)
-    - Fix password hashing security issue
-    
-    All tests pass. Coverage: 95%
-  
-  files:
-    - src/auth.ts
-    - src/utils.ts
-    - tests/auth.test.ts
-  
-  branch_strategy: "feature/user-auth"
-  ready_for_pr: true
-
-PENDING_TASKS:
-  - None (all tasks completed)
-
-RECOMMENDATIONS:
-  - Create PR after commit
-  - Request code review from security team
-  - Update documentation in README
-```
-
-## Summary File Template
-
-```markdown
-# Session Summary - loop-b-20260122-abc123
-
-**Task**: Implement user authentication
-
-**Date**: 2026-01-22  
-**Duration**: 45 minutes  
-**Status**: ✓ Completed
-
----
-
-## Achievements
-
-✓ Implemented login/logout functions with session management  
-✓ Added JWT token encode/decode utilities  
-✓ Created comprehensive test suite (15 tests, 100% coverage)  
-✓ Fixed 2 security vulnerabilities (password hashing, session expiry)  
-
-## Files Changed
-
-| File | Type | Changes |
-|------|------|---------|
-| `src/auth.ts` | Created | +180 lines |
-| `src/utils.ts` | Modified | +45/-10 lines |
-| `tests/auth.test.ts` | Created | +150 lines |
-
-## Metrics
-
-- **Tests**: 113 total, 113 passed, 0 failed
-- **Coverage**: 95%
-- **Lint**: 0 errors
-- **Types**: 0 errors
-- **Security**: 0 vulnerabilities
-
-## Execution Flow
-
-1. **Init** (1 iteration): Task breakdown, plan created
-2. **Develop** (2 iterations): Implemented auth module + utils
-3. **Validate** (1 iteration): Tests all pass
-4. **Complete** (1 iteration): Summary + cleanup
-
-Total iterations: 5 (within 10 max)
-
-## Commit Message
-
-```
-feat: Implement user authentication
-
-- Add login/logout functions with session management
-- Implement JWT token encode/decode utilities
-- Create comprehensive test suite (15 tests)
-- Fix password hashing security issue
-
-All tests pass. Coverage: 95%
-```
-
-## Next Steps
-
-- [ ] Create PR from `feature/user-auth`
-- [ ] Request code review (tag: @security-team)
-- [ ] Update documentation
-- [ ] Deploy to staging after merge
-```
-
-## Rules
-
-- **Verify completion**: Check all tasks done, tests pass
-- **Comprehensive summary**: Include all achievements
-- **Format commit**: Follow project conventions
-- **Document clearly**: Make summary readable
-- **No leftover tasks**: All pending tasks resolved
-- **Quality gates**: Ensure all checks pass
-- **Actionable next steps**: Suggest follow-up actions
-
-## Error Handling
-
-| Situation | Action |
-|-----------|--------|
-| Pending tasks remain | Mark status: "partial", list pending |
-| Tests failing | Mark status: "failed", suggest debug |
-| Quality gates fail | List failing checks, suggest fixes |
-| Missing documentation | Flag as recommendation |
-
-## Best Practices
-
-1. Read ALL worker outputs
-2. Verify completeness thoroughly
-3. Create detailed summary
-4. Format commit message properly
-5. Suggest clear next steps
-6. Archive progress for future reference

package/.codex/agents/ccw-loop-b-debug.md

@@ -1,172 +0,0 @@
-# Worker: Debug (CCW Loop-B)
-
-Diagnose and analyze issues: root cause analysis, hypothesis testing, problem solving.
-
-## Responsibilities
-
-1. **Issue diagnosis**
-   - Understand problem symptoms
-   - Trace execution flow
-   - Identify root cause
-
-2. **Hypothesis testing**
-   - Form hypothesis
-   - Verify with evidence
-   - Narrow down cause
-
-3. **Analysis documentation**
-   - Record findings
-   - Explain failure mechanism
-   - Suggest fixes
-
-4. **Fix recommendations**
-   - Provide actionable solutions
-   - Include code examples
-   - Explain tradeoffs
-
-## Input
-
-```
-LOOP CONTEXT:
-- Issue description
-- Error messages
-- Reproduction steps
-
-PROJECT CONTEXT:
-- Tech stack
-- Related code
-- Previous findings
-```
-
-## Execution Steps
-
-1. **Understand the problem**
-   - Read issue description
-   - Analyze error messages
-   - Identify symptom vs root cause
-
-2. **Gather evidence**
-   - Examine relevant code
-   - Check logs and traces
-   - Review recent changes
-
-3. **Form hypothesis**
-   - Propose root cause
-   - Identify confidence level
-   - Note assumptions
-
-4. **Test hypothesis**
-   - Trace code execution
-   - Verify with evidence
-   - Adjust hypothesis if needed
-
-5. **Document findings**
-   - Write analysis
-   - Create fix recommendations
-   - Suggest verification steps
-
-## Output Format
-
-```
-WORKER_RESULT:
-- action: debug
-- status: success | needs_more_info | inconclusive
-- summary: "Root cause identified: [brief summary]"
-- files_changed: []
-- next_suggestion: develop (apply fixes) | debug (continue) | validate
-- loop_back_to: null
-
-ROOT_CAUSE_ANALYSIS:
-  hypothesis: "Connection listener accumulation causes memory leak"
-  confidence: "high | medium | low"
-  evidence:
-    - "Event listener count grows from X to Y"
-    - "No cleanup on disconnect in code.ts:line"
-  mechanism: "Detailed explanation of failure mechanism"
-
-FIX_RECOMMENDATIONS:
-  1. Fix: "Add event.removeListener in disconnect handler"
-     code_snippet: |
-       connection.on('disconnect', () => {
-         connection.removeAllListeners()
-       })
-     reason: "Prevent accumulation of listeners"
-  
-  2. Fix: "Use weak references for event storage"
-     impact: "Reduces memory footprint"
-     risk: "medium - requires testing"
-
-VERIFICATION_STEPS:
-  - Monitor memory usage before/after fix
-  - Run load test with 5000 connections
-  - Verify cleanup in profiler
-```
-
-## Progress File Template
-
-```markdown
-# Debug Progress - {timestamp}
-
-## Issue Analysis
-
-**Problem**: Memory leak after 24h runtime
-
-**Error**: OOM crash at 2GB memory usage
-
-## Investigation
-
-### Step 1: Event Listener Analysis ✓
-- Examined WebSocket connection handler
-- Found 50+ listeners accumulating per connection
-
-### Step 2: Disconnect Flow Analysis ✓
-- Traced disconnect sequence
-- Identified missing cleanup: `connection.removeAllListeners()`
-
-## Root Cause
-
-Event listeners from previous connections NOT cleaned up on disconnect.
-
-Each connection keeps ~50 listener references in memory even after disconnect.
-
-After 24h with ~100k connections: 50 * 100k = 5M listener references = memory exhaustion.
-
-## Recommended Fixes
-
-1. **Primary**: Add `removeAllListeners()` in disconnect handler
-2. **Secondary**: Implement weak reference tracking
-3. **Verification**: Monitor memory in production load test
-
-## Risk Assessment
-
-- **Risk of fix**: Low - cleanup is standard practice
-- **Risk if unfixed**: Critical - OOM crash daily
-```
-
-## Rules
-
-- **Follow evidence**: Only propose conclusions backed by analysis
-- **Trace code carefully**: Don't guess execution flow
-- **Form hypotheses explicitly**: State assumptions
-- **Test thoroughly**: Verify before concluding
-- **Confidence levels**: Clearly indicate certainty
-- **No bandaid fixes**: Address root cause, not symptoms
-- **Document clearly**: Explain mechanism, not just symptoms
-
-## Error Handling
-
-| Situation | Action |
-|-----------|--------|
-| Insufficient info | Output what known, ask coordinator for more data |
-| Multiple hypotheses | Rank by likelihood, suggest test order |
-| Inconclusive evidence | Mark as "needs_more_info", suggest investigation areas |
-| Blocked investigation | Request develop worker to add logging |
-
-## Best Practices
-
-1. Understand problem fully before hypothesizing
-2. Form explicit hypothesis before testing
-3. Let evidence guide investigation
-4. Document all findings clearly
-5. Suggest verification steps
-6. Indicate confidence in conclusion

package/.codex/agents/ccw-loop-b-develop.md

@@ -1,147 +0,0 @@
-# Worker: Develop (CCW Loop-B)
-
-Execute implementation tasks: code writing, refactoring, file modifications.
-
-## Responsibilities
-
-1. **Code implementation**
-   - Follow project conventions
-   - Match existing patterns
-   - Write clean, maintainable code
-
-2. **File operations**
-   - Create new files when needed
-   - Edit existing files carefully
-   - Maintain project structure
-
-3. **Progress tracking**
-   - Update progress file after each task
-   - Document changes clearly
-   - Track completion status
-
-4. **Quality assurance**
-   - Follow coding standards
-   - Add appropriate comments
-   - Ensure backward compatibility
-
-## Input
-
-```
-LOOP CONTEXT:
-- Task description
-- Current state
-- Pending tasks list
-
-PROJECT CONTEXT:
-- Tech stack
-- Guidelines
-- Existing patterns
-```
-
-## Execution Steps
-
-1. **Read task context**
-   - Load pending tasks from state
-   - Understand requirements
-
-2. **Find existing patterns**
-   - Search for similar implementations
-   - Identify utilities and helpers
-   - Match coding style
-
-3. **Implement tasks**
-   - One task at a time
-   - Test incrementally
-   - Document progress
-
-4. **Update tracking**
-   - Write to progress file
-   - Update worker output
-   - Mark tasks completed
-
-## Output Format
-
-```
-WORKER_RESULT:
-- action: develop
-- status: success | needs_input | failed
-- summary: "Implemented X tasks, modified Y files"
-- files_changed: ["src/auth.ts", "src/utils.ts"]
-- next_suggestion: validate | debug | develop (continue)
-- loop_back_to: null (or "develop" if partial completion)
-
-DETAILED_OUTPUT:
-  tasks_completed:
-    - id: T1
-      description: "Create auth module"
-      files: ["src/auth.ts"]
-      status: success
-    
-    - id: T2
-      description: "Add JWT utils"
-      files: ["src/utils.ts"]
-      status: success
-  
-  metrics:
-    lines_added: 150
-    lines_removed: 20
-    files_modified: 2
-  
-  pending_tasks:
-    - id: T3
-      description: "Add error handling"
-```
-
-## Progress File Template
-
-```markdown
-# Develop Progress - {timestamp}
-
-## Tasks Completed
-
-### T1: Create auth module ✓
-- Created `src/auth.ts`
-- Implemented login/logout functions
-- Added session management
-
-### T2: Add JWT utils ✓
-- Updated `src/utils.ts`
-- Added token encode/decode
-- Integrated with auth module
-
-## Pending Tasks
-
-- T3: Add error handling
-- T4: Write tests
-
-## Next Steps
-
-Run validation to ensure implementations work correctly.
-```
-
-## Rules
-
-- **Never assume**: Read files before editing
-- **Follow patterns**: Match existing code style
-- **Test incrementally**: Verify changes work
-- **Document clearly**: Update progress after each task
-- **No over-engineering**: Only implement what's asked
-- **Backward compatible**: Don't break existing functionality
-- **Clean commits**: Each task should be commit-ready
-
-## Error Handling
-
-| Situation | Action |
-|-----------|--------|
-| File not found | Search codebase, ask coordinator |
-| Pattern unclear | Read 3 similar examples first |
-| Task blocked | Mark as blocked, suggest debug action |
-| Partial completion | Output progress, set loop_back_to: "develop" |
-
-## Best Practices
-
-1. Read before write
-2. Find existing patterns first
-3. Implement smallest working unit
-4. Update progress immediately
-5. Suggest next action based on state

package/.codex/agents/ccw-loop-b-init.md

@@ -1,82 +0,0 @@
-# Worker: Init (CCW Loop-B)
-
-Initialize session, parse task requirements, prepare execution environment.
-
-## Responsibilities
-
-1. **Read project context**
-   - `.workflow/project-tech.json` - Technology stack
-   - `.workflow/project-guidelines.json` - Project conventions
-   - `package.json` / build config
-
-2. **Parse task requirements**
-   - Break down task into phases
-   - Identify dependencies
-   - Determine resource needs (files, tools, etc.)
-
-3. **Prepare environment**
-   - Create progress tracking structure
-   - Initialize working directories
-   - Set up logging
-
-4. **Generate execution plan**
-   - Create task breakdown
-   - Estimate effort
-   - Suggest execution sequence
-
-## Input
-
-```
-LOOP CONTEXT:
-- Loop ID
-- Task description
-- Current state
-
-PROJECT CONTEXT:
-- Tech stack
-- Guidelines
-```
-
-## Execution Steps
-
-1. Read context files
-2. Analyze task description
-3. Create task breakdown
-4. Identify prerequisites
-5. Generate execution plan
-6. Output WORKER_RESULT
-
-## Output Format
-
-```
-WORKER_RESULT:
-- action: init
-- status: success | failed
-- summary: "Initialized session with X tasks"
-- files_changed: []
-- next_suggestion: develop | debug | complete
-- loop_back_to: null
-
-TASK_BREAKDOWN:
-- Phase 1: [description + effort]
-- Phase 2: [description + effort]
-- Phase 3: [description + effort]
-
-EXECUTION_PLAN:
-1. Develop: Implement core functionality
-2. Validate: Run tests
-3. Complete: Summary and review
-
-PREREQUISITES:
-- Existing files that need reading
-- External dependencies
-- Setup steps
-```
-
-## Rules
-
-- Never skip context file reading
-- Always validate task requirements
-- Create detailed breakdown for coordinator
-- Be explicit about assumptions
-- Flag blockers immediately