generator-build-worker

Estrelas13

Forks1

Atualizado2 de maio de 2026 às 07:03

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

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

redker56

redker56/auto-harness

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

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.

Mais deste repositório

mesmo repositório

evaluator-review-contract-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

2026-05-0213

evaluator-write-final-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.

2026-05-0213

evaluator-write-qa-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluator_qa_parallel.

2026-05-0213

evaluator-write-retest-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluator_retest_parallel.

2026-05-0213

generator-build-integrator

redker56/auto-harness

Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.

2026-05-0213

generator-draft-contract-parallel

redker56/auto-harness

Internal Auto-Harness generator skill for parallel sprint contract drafting. Use only inside the Generator subagent when it is producing or revising the current parallel sprint contract.

2026-05-0213

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.