Menú
Task execution templates and coding engine dispatch patterns for coding tasks.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Branch, commit, push, and open PRs with humanized messages, then monitor GitHub Actions CI. Per-project autonomy gating; blocks direct pushes to the default branch and pushes with a dirty tree. Never auto-merges.
Dispatch patterns for Claude Code as the coding engine. Default harness. Implementation dispatches go through dispatch_coder.py (writes the dispatch receipt the commit gate requires).
Testing strategy, TDD enforcement, spec compliance, and regression checks.
Write implementation plans: bite-sized tasks for coding engine dispatch.
Automated fix loop for failed Quality/Reviewer checks. Parses failures, builds escalating prompts, dispatches through the active harness up to 3 times.
Run independent, file-disjoint plan tasks concurrently, each isolated in its own git worktree + branch. Collects per-task results; never auto-merges.
Basado en la clasificación ocupacional SOC
| name | implementer |
| description | Task execution templates and coding engine dispatch patterns for coding tasks. |
| version | 2.0.0 |
| author | Hermes Coder (adapted from Squad booster/dsky) |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["implementation","coding","dispatch","execution"],"related_skills":["architect","quality","writing-plans","harness-claude-code","harness-antigravity","harness-opencode"]}} |
Apply this lens when dispatching coding tasks to the coding engine and structuring implementation prompts.
Identity: Implementation specialist who translates plans into precise coding engine dispatch prompts.
Expertise:
Responsibilities:
Consult the active harness skill (under skills/harness/) for the exact terminal() command syntax. The prompts below work with any harness.
Dispatch to the coding engine:
<file>, update <function> to <change>. Run existing tests to verify."Dispatch to the coding engine:
<feature> as described: <spec>. Create files in <location>. Write tests in <test-location>. Follow existing patterns in <example-file>."Dispatch to the coding engine:
<description>. Reproduce with: <repro-steps>. Root cause is likely in <file>. Add a regression test."Dispatch to the coding engine:
<component>: <goal>. Preserve all existing behavior. Run tests after each change."