Skip to content
Automation
Skill

/generator-build-worker

Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.

From plugin
auto-harness
1420 skills26 agents8 commands5 hooks
+1
Install
$ npx -y skills add redker56/auto-harness --skill generator-build-worker --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/generator-build-worker

Context preview

The summary Claude sees to decide when to auto-load this skill.

Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.

SKILL.md

generator-build-worker.SKILL.md
name: generator-build-worker
description: Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.
user-invocable: false

Generator Build Worker

This skill governs a worktree-bound Generator **build worker**.

At the start of this action, read these local harness artifacts from the worktree snapshot:

  • `.harness-parallel/status.md`
  • `.harness-parallel/intake.md`
  • `.harness-parallel/spec.md`
  • `.harness-parallel/design-direction.md`
  • `.harness-parallel/contracts/sprint-XX-contract.md`
  • `.harness-parallel/contracts/sprint-XX-review.md` when it exists for the current sprint

Then inspect the current project implementation relevant to this action:

  • Read the assigned owned files or globs first.
  • Read neighboring files only as dependency context unless the Orchestrator explicitly assigned them to you.
  • Treat this worktree as isolated. Do not assume other worker changes already exist here unless they were merged into the base before the worktree was created.

Follow these rules:

  • Implement only the assigned dependency-graph node.
  • Modify only the owned files or globs named by the Orchestrator.
  • Do not modify `.harness-parallel/` files.
  • Run targeted verification for your node before finishing.
  • Make a local git commit in this worktree.
  • If your task cannot be completed without touching an unowned path, stop short of freelancing and report the blocker clearly.
Read more
Ships withauto-harness

Auto-Harness is a Claude Code plugin for longer software tasks that need planning, implementation, QA, fixes, retests, and a final report. Give it a product brief.

Get the whole plugin

Other skills on auto-harness.