clink-codex-delegate

# Clink Codex Task Delegation Guide

When delegating tasks to clink codex, treat it like a junior developer. This skill provides a standardized approach to task assignment.

## 🎯 Core Principles

### What to Delegate to Clink Codex
Clink Codex can handle **all types of coding tasks**:

- ✅ **Implementation tasks**: Writing code logic, functions, components
- ✅ **Code generation**: Creating new files, modules, classes
- ✅ **Logic implementation**: Business logic, algorithms, data processing
- ✅ **Research & Analysis**: Investigating architecture, analyzing codebases
- ✅ **Design**: System design, architecture decisions
- ✅ **Testing**: Writing tests, running tests, debugging
- ✅ **Code Review**: Reviewing code quality, best practices
- ✅ **Documentation**: Writing docs, comments, READMEs
- ✅ **Refactoring**: Code optimization, restructuring
- ✅ **Bug fixing**: Debugging and resolving issues

### Important: Provide Full Context
When delegating any task, always provide:
- **Project context**: What the project does, tech stack, conventions
- **Relevant files**: Paths to files that need to be read/modified
- **Dependencies**: Related modules, APIs, or external services
- **Constraints**: Any limitations or requirements to follow

## 📝 Your Responsibilities (After Clink Codex Completes Task)
1. **Verify** the output meets requirements
2. **Validate** the code works as expected
3. **Integrate** the changes into the project
4. **Iterate** if needed - provide specific feedback and re-delegate

## ⚠️ Important Notes
- **Provide full context** - Codex works best with comprehensive information
- **Be specific** - Clear requirements lead to better results
- **If codex fails** - Switch to **clink gemini** as fallback (see Fallback section below)
- **If code doesn't meet requirements** - Provide specific feedback and re-delegate

---

## 📋 Standard Task Brief Template

Use this template when delegating tasks to clink codex:

```markdown
## 🎯 Task Title

Implement [specific fea