Swarm Implement

Phase 3 - Implement in scoped units

Implement in coherent, reviewable chunks. Follow existing repository patterns.

declare_scope discipline. Before every coder or test-engineer delegation (and before every retry), call declare_scope({ taskId, files, replace_existing: true }) with the exact workspace-relative file list the delegated agent may modify — including generated or lockfile paths the change will produce (for example, dist/*, package-lock.json, or bun.lock). Direct and shell writes are both scope-enforced. If the file list is not completely obvious, declare the containing workspace-relative directories instead. Treat SCOPE_CONFLICT, SCOPE_BINDING_EXPIRED, SCOPE_BINDING_AMBIGUOUS, and SCOPE_WORKSPACE_MISMATCH as architect-owned recovery signals: reconcile the named scope sources or lane root, replace the declaration, then redispatch. Never instruct the delegated agent to bypass the gate or switch write mechanisms.

Smallest justified scope on SCOPE_CONFLICT (issue #1994 S4). The replacement declaration must be the SMALLEST justified scope: first reconcile what the delegation actually intends to write (the task's files vs the conflicting scope source named in the diagnostic), then narrow the conflicting lower-precedence source to a subset of that list — repair stale plan scope with save_plan and/or the delegation's FILE: lines — and only then re-declare exactly that file list; re-declaring alone leaves the non-subset relation and reproduces the same SCOPE_CONFLICT. Split the task into separate delegations if the conflict reveals two disjoint write sets. NEVER resolve a SCOPE_CONFLICT by widening to a plan-inferred superset: auto-widening over-authorizes writes and hides an inaccurate plan or delegation prompt behind a bigger scope. This matches the execute skill's scope-recovery contract ("Do not widen scope just to make the sets agree"); a save_plan scope repair is a bookkeeping change covered by the critic-gate plan-freeze rule.

If the project exposes sast_scan with capture_baseline, capture the phase-scoped SAST baseline before first coder delegation so later scans fail only on new findings rather than pre-existing infrastructure noise.

Phase 4 - Objective validation

Run the strongest objective checks available for the task: tests, lint, typecheck, build, targeted repro scripts, and local runtime verification where relevant. If you cannot verify it, do not claim it is done.

Phase 5 - Independent reviewer validation

Use an independent reviewer subagent when the task edits code, tests, docs, package metadata, release notes, or skill files. The reviewer must inspect the actual current diff and validation evidence after implementation. Any later edit invalidates approval and requires re-review.

Reviewer responsibilities:

• inspect the implementation with fresh context,
• look for correctness bugs, edge cases, regressions, claim-vs-actual mismatches, and test blind spots,
• default to disbelief until evidence supports the change,
• classify issues as CONFIRMED, DISPROVED, UNVERIFIED, or PRE_EXISTING when useful,
• verify that at least one regression test in the diff has falsification evidence when the task claims regression coverage: the fix was temporarily removed or bypassed, the test failed for the expected reason, the fix was restored, and the test passed again. If no regression test is applicable, the reviewer must record why,
• return APPROVE, NEEDS_REVISION, or BLOCKED.

NEEDS_REVISION or BLOCKED blocks completion until fixed and re-reviewed.

Phase 6 - Critic challenge

Use a critic subagent after independent reviewer approval for any task that edits code, tests, docs, package metadata, release notes, or skill files. The critic must challenge the reviewer-approved current diff and evidence. Any later edit invalidates critic approval and requires another critic pass.

Phase 7 - Final synthesis

Before calling work complete, verify:

• objective validation ran and results were recorded,
• the independent reviewer approved the latest diff and evidence,
• a separate critic approved after reviewer approval,
• every NEEDS_REVISION or BLOCKED item was fixed and re-reviewed,
• no edit occurred after the latest reviewer/critic approval,
• no behavior is unwired or deferred without explicit user instruction.

Adapter notes

Runtime-specific adapter skills in .claude/skills/swarm-implement/ and .agents/skills/swarm-implement/ must stay thin and delegate to this canonical .opencode workflow.