agent-tasklisted

# Agent Task Use this skill when the user wants Codex to delegate a bounded implementation, research, or exploration task to an external agent. ## Rules - Codex remains the primary conversation and final reviewer. - Create a task packet before launching any external agent. - Keep the task narrow enough for one result file and one optional patch. - Do not paste or log secrets, API keys, launcher contents, or provider environment variables. - External agents should write outputs into the task folder. - Do not claim the delegated task is complete until Codex has collected and reviewed result files. ## Workflow 1. Identify the workspace root and allowed paths. 2. Choose `claude-code`, `reasonix`, or `manual`. 3. Run `New-AgentTask.ps1` with the task, context, mode, target agent, and workspace root. 4. For implementation work where the external agent may edit repository files, create an isolated worktree before launch. See `Isolation For Implementation Tasks`. 5. Launch the selected agent: - Formal non-interactive worker: `Invoke-AgentTask.ps1` after isolated worktree creation. It dispatches to Claude Code or Reasonix from `target_agent`. - Claude Code direct compatibility runner: `Invoke-ClaudeCodeTask.ps1` - Reasonix direct compatibility runner: `Invoke-ReasonixTask.ps1` - Reasonix worker execution expects the `reasonix` CLI to be on PATH, or `REASONIX_COMMAND` / `-ReasonixCommand` to point to the real CLI shim. - Close Reasonix Desktop before a CLI worker run. The runner p