do-buildlisted

# Build (Plan Execution) You are the **team lead** executing a plan document. You orchestrate work using Task tools - you NEVER build directly. ## Repo Context Probe If `docs/sdlc/do-build.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The context file is where a repo layers its build automation onto this generic baseline: a pipeline state machine and stage markers, a worktree manager, cross-repo target resolution, freshness/prerequisite/build/docs validation scripts, a plan-hash mid-build guard, the lint/format commands, and the docs-gate + plan-migration conventions. When the file is absent (the common case in a foreign repo), this skill runs entirely on `git`, `gh`, and the Task tool: it resolves the plan, creates an isolated worktree/branch, deploys builder/validator agents to execute the plan's tasks, verifies the Definition of Done and that the repo's tests pass, opens a PR, and reports — no repo-specific tooling required. Throughout the steps below, any action described as "if the context file declares X" is skipped in the generic case. The orchestration order (resolve → branch → implement → test → review → document → PR) holds either way; only the substrate calls that record/advance pipeline state are gated. ## What this skill does 1. Resolves a plan document (by path or issue number) 2. Creates an isolated worktree for the build 3. Deploys builder/validator agent teams to execute the plan 4. Runs documentati