coding-agentlisted

# /coding-agent — Delegate Coding Work Delegate coding tasks to subagents or run Claude Code/Codex in separate tmux sessions on the host. Choose the right pattern for the job. ## When to use each pattern | Situation | Pattern | |-----------|---------| | Bounded task with clear spec (fix bug, implement feature, write tests) | Task tool (subagent) | | Long-running interactive session, needs persistence | tmux + `claude --dangerously-skip-permissions` | | PR review — checkout and inspect | tmux + clone to `/tmp` | | Multiple independent fixes in parallel | tmux + git worktrees | | Claude Code capped or erroring | tmux + Codex fallback | --- ## Pattern 1: Task Tool (Primary Pattern) Use the `Task` tool to delegate focused coding work to a subagent. The subagent runs inside the same SDK session with full tool access (Bash, Read, Write, Edit, Glob, Grep). This is the default choice for most coding tasks. ### When to use - Implement a feature, fix a bug, write tests - Refactor a module or file - Analyse a codebase and produce a report - Any multi-step work that needs tool use but doesn't require an interactive terminal ### How to invoke ``` Task({ description: "Fix the rate-limiting bug in the API gateway", prompt: "..." }) ``` ### Prompt template Write the Task prompt as a complete standalone brief. The subagent has no memory of the conversation that spawned it. Include: 1. **What to do** — specific, unambiguous objective 2. **Where to work** — directory, repo, rel