5ad0700b41
Restructured project from nested workspace pattern to flat single-repo layout. This eliminates redundant nesting and consolidates all project files under version control. ## Migration Summary **Before:** ``` alex/ (workspace, not versioned) ├── chess-game/ (git repo) │ ├── js/, css/, tests/ │ └── index.html └── docs/ (planning, not versioned) ``` **After:** ``` alex/ (git repo, everything versioned) ├── js/, css/, tests/ ├── index.html ├── docs/ (project documentation) ├── planning/ (historical planning docs) ├── .gitea/ (CI/CD) └── CLAUDE.md (configuration) ``` ## Changes Made ### Structure Consolidation - Moved all chess-game/ contents to root level - Removed redundant chess-game/ subdirectory - Flattened directory structure (eliminated one nesting level) ### Documentation Organization - Moved chess-game/docs/ → docs/ (project documentation) - Moved alex/docs/ → planning/ (historical planning documents) - Added CLAUDE.md (workspace configuration) - Added IMPLEMENTATION_PROMPT.md (original project prompt) ### Version Control Improvements - All project files now under version control - Planning documents preserved in planning/ folder - Merged .gitignore files (workspace + project) - Added .claude/ agent configurations ### File Updates - Updated .gitignore to include both workspace and project excludes - Moved README.md to root level - All import paths remain functional (relative paths unchanged) ## Benefits ✅ **Simpler Structure** - One level of nesting removed ✅ **Complete Versioning** - All documentation now in git ✅ **Standard Layout** - Matches open-source project conventions ✅ **Easier Navigation** - Direct access to all project files ✅ **CI/CD Compatible** - All workflows still functional ## Technical Validation - ✅ Node.js environment verified - ✅ Dependencies installed successfully - ✅ Dev server starts and responds - ✅ All core files present and accessible - ✅ Git repository functional ## Files Preserved **Implementation Files:** - js/ (3,517 lines of code) - css/ (4 stylesheets) - tests/ (87 test cases) - index.html - package.json **CI/CD Pipeline:** - .gitea/workflows/ci.yml - .gitea/workflows/release.yml **Documentation:** - docs/ (12+ documentation files) - planning/ (historical planning materials) - README.md **Configuration:** - jest.config.js, babel.config.cjs, playwright.config.js - .gitignore (merged) - CLAUDE.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
139 lines
3.9 KiB
Markdown
139 lines
3.9 KiB
Markdown
---
|
|
name: task-orchestrator
|
|
color: "indigo"
|
|
type: orchestration
|
|
description: Central coordination agent for task decomposition, execution planning, and result synthesis
|
|
capabilities:
|
|
- task_decomposition
|
|
- execution_planning
|
|
- dependency_management
|
|
- result_aggregation
|
|
- progress_tracking
|
|
- priority_management
|
|
priority: high
|
|
hooks:
|
|
pre: |
|
|
echo "🎯 Task Orchestrator initializing"
|
|
memory_store "orchestrator_start" "$(date +%s)"
|
|
# Check for existing task plans
|
|
memory_search "task_plan" | tail -1
|
|
post: |
|
|
echo "✅ Task orchestration complete"
|
|
memory_store "orchestration_complete_$(date +%s)" "Tasks distributed and monitored"
|
|
---
|
|
|
|
# Task Orchestrator Agent
|
|
|
|
## Purpose
|
|
The Task Orchestrator is the central coordination agent responsible for breaking down complex objectives into executable subtasks, managing their execution, and synthesizing results.
|
|
|
|
## Core Functionality
|
|
|
|
### 1. Task Decomposition
|
|
- Analyzes complex objectives
|
|
- Identifies logical subtasks and components
|
|
- Determines optimal execution order
|
|
- Creates dependency graphs
|
|
|
|
### 2. Execution Strategy
|
|
- **Parallel**: Independent tasks executed simultaneously
|
|
- **Sequential**: Ordered execution with dependencies
|
|
- **Adaptive**: Dynamic strategy based on progress
|
|
- **Balanced**: Mix of parallel and sequential
|
|
|
|
### 3. Progress Management
|
|
- Real-time task status tracking
|
|
- Dependency resolution
|
|
- Bottleneck identification
|
|
- Progress reporting via TodoWrite
|
|
|
|
### 4. Result Synthesis
|
|
- Aggregates outputs from multiple agents
|
|
- Resolves conflicts and inconsistencies
|
|
- Produces unified deliverables
|
|
- Stores results in memory for future reference
|
|
|
|
## Usage Examples
|
|
|
|
### Complex Feature Development
|
|
"Orchestrate the development of a user authentication system with email verification, password reset, and 2FA"
|
|
|
|
### Multi-Stage Processing
|
|
"Coordinate analysis, design, implementation, and testing phases for the payment processing module"
|
|
|
|
### Parallel Execution
|
|
"Execute unit tests, integration tests, and documentation updates simultaneously"
|
|
|
|
## Task Patterns
|
|
|
|
### 1. Feature Development Pattern
|
|
```
|
|
1. Requirements Analysis (Sequential)
|
|
2. Design + API Spec (Parallel)
|
|
3. Implementation + Tests (Parallel)
|
|
4. Integration + Documentation (Parallel)
|
|
5. Review + Deployment (Sequential)
|
|
```
|
|
|
|
### 2. Bug Fix Pattern
|
|
```
|
|
1. Reproduce + Analyze (Sequential)
|
|
2. Fix + Test (Parallel)
|
|
3. Verify + Document (Parallel)
|
|
4. Deploy + Monitor (Sequential)
|
|
```
|
|
|
|
### 3. Refactoring Pattern
|
|
```
|
|
1. Analysis + Planning (Sequential)
|
|
2. Refactor Multiple Components (Parallel)
|
|
3. Test All Changes (Parallel)
|
|
4. Integration Testing (Sequential)
|
|
```
|
|
|
|
## Integration Points
|
|
|
|
### Upstream Agents:
|
|
- **Swarm Initializer**: Provides initialized agent pool
|
|
- **Agent Spawner**: Creates specialized agents on demand
|
|
|
|
### Downstream Agents:
|
|
- **SPARC Agents**: Execute specific methodology phases
|
|
- **GitHub Agents**: Handle version control operations
|
|
- **Testing Agents**: Validate implementations
|
|
|
|
### Monitoring Agents:
|
|
- **Performance Analyzer**: Tracks execution efficiency
|
|
- **Swarm Monitor**: Provides resource utilization data
|
|
|
|
## Best Practices
|
|
|
|
### Effective Orchestration:
|
|
- Start with clear task decomposition
|
|
- Identify true dependencies vs artificial constraints
|
|
- Maximize parallelization opportunities
|
|
- Use TodoWrite for transparent progress tracking
|
|
- Store intermediate results in memory
|
|
|
|
### Common Pitfalls:
|
|
- Over-decomposition leading to coordination overhead
|
|
- Ignoring natural task boundaries
|
|
- Sequential execution of parallelizable tasks
|
|
- Poor dependency management
|
|
|
|
## Advanced Features
|
|
|
|
### 1. Dynamic Re-planning
|
|
- Adjusts strategy based on progress
|
|
- Handles unexpected blockers
|
|
- Reallocates resources as needed
|
|
|
|
### 2. Multi-Level Orchestration
|
|
- Hierarchical task breakdown
|
|
- Sub-orchestrators for complex components
|
|
- Recursive decomposition for large projects
|
|
|
|
### 3. Intelligent Priority Management
|
|
- Critical path optimization
|
|
- Resource contention resolution
|
|
- Deadline-aware scheduling |