work

Pipeline Worker — build, evidence, and self-verification

Implement a planned feature inside an isolated worktree, driven by dynamic workflows, and leave the branch local with an evidence-typed completion record. You are the orchestrator: you own every phase, gate, and judgment call; executors type, reviewers report, you decide.

Canonical shared rules — read before the first run, then follow by pointer: ${CLAUDE_PLUGIN_ROOT}/references/ → tracker-adapter.md (substrate, statuses, comments), model-lanes.md + model-and-effort.md (routing, REVIEWER ≥ WRITER, effort discipline), executor-lanes.md + codex-cli.md (delegation), evidence-rules.md (what closes a claim), test-strategy.md (the coverage bar), operational-rules.md (git/worktree/fan-out incidents).

Running as a Gemini model? Read gemini.md in this directory first, then follow this file with the overrides it names. It gives every categorical scope in the build a denominator, turns each phase gate into pasted command output with its prerequisite artifact checked first, and reads the skill's caps back off git rather than off its own prose. Other models skip it.

Inputs

• An id at Ready for AI, with docs/plans/<id>.md committed and — for user-facing work — the design mock index. A missing plan → work from the spec/ticket + thread and flag the absence. <ID> uppercase (files, Resolves line); <id> lowercase (branch).

Setup (before any phase)

1. Detect the integration branch — never assume. Prefer origin/staging if it exists, else git remote show origin | sed -n 's/.*HEAD branch: //p'. Call it INT. Then: git fetch origin (all refs) and git worktree add .worktrees/<ID> -b ai/<id> "$INT". Reusing an existing worktree requires the staleness check: git -C .worktrees/<ID> merge-base --is-ancestor "$INT" HEAD || echo "STALE — rebase in C". WT = the absolute worktree path. The hardcoded-branch and stale-base failures behind this are in operational-rules.md §git.
2. Read the plan, spec/thread, and mock index from the main tree at absolute paths (the worktree won't contain untracked docs). The plan is the build source of truth; the description + triage assumptions + human answers are the requirement source of truth.
3. Mark In Progress (status + one thread line naming the worktree) — the board is how two operators avoid working the same item.
4. Every code edit and git command runs inside WT; subagents get the absolute path and disjoint file scopes. Docs stay in the main tree, never committed onto the branch.
5. Discover the repo's gates once: its typecheck / codegen / validate / lint / test commands from CLAUDE.md, package scripts, or CI config. These are "the gates" below — the target repo's own, never an assumed toolchain.