agent-output-reconciler ยท diff
git:20261002.92631e4 to git:20261016.a802ce4
10 added, 78 removed. Audit A to A.
---
name: agent-output-reconciler
- description: Use when multiple agent results must be checked for missing evidence, scope drift, contradictions, and merge conflicts before an acceptance decision.
+ description: Use when a plan, prompt, or doc still names agent-output-reconciler. Since 0.6.0 reconciliation is step 1 of agent-acceptance-gate; this redirect stub is removed in 0.7.0.
---
- # agent-output-reconciler
-
- Reconcile completed task results into one evidence-based report. This skill
- describes what happened and what conflicts remain. It does not accept work,
- merge changes, retry tasks, or write canonical memory.
-
- ## Inputs
-
- - the current plan and its task IDs, roles, scopes, dependencies, and success
- criteria;
- - each task packet, result summary, structured result, and raw-log path;
- - the relevant `TaskCheckpoint` and latest `PolicyDecision`;
- - repository diff and test evidence.
-
- Current plans use provider-neutral roles: `primary-agent`,
- `delegated-executor`, `reviewer`, and `synthesizer`. Historical provider fields
- may be parsed for migration only and must not influence current routing.
-
- ## Workflow
-
- 1. Validate the plan and checkpoint. If either is unreadable, stop and report a
- blocker. Do not infer missing policy values.
- 2. Inventory every planned task. Preserve `null`, missing, cancelled,
- declined, degraded, and failed results as distinct states.
- 3. Filter unusable payloads before synthesis, while retaining a record of what
- was filtered and why. Never turn a completed prose result into `null` merely
- because an optional structured-output step failed.
- 4. Compare actual changed files with each task's declared scope. Record
- justified transitive changes separately from unexplained drift.
- 5. Verify claimed tests and artifacts from their evidence references. A result
- without evidence remains unverified even if its prose says "success".
- 6. Identify file collisions, incompatible assumptions, contradictory findings,
- dependency-order violations, and unresolved risks.
- 7. Compose a reconciliation report using
- `references/reconciliation_template.md`.
- 8. Hand the report to `agent-acceptance-gate`. Do not convert a reconciliation
- recommendation into an acceptance decision.
-
- Use the [task-content evidence review](../../docs/task-content-evidence.md) to
- bind each result to the current task, run/attempt, baseline, and independently
- observed candidate. Preserve stale or wrong-task evidence as unverified. Account
- for existing dirty state and parallel writers before attributing a delta. An
- unchanged result needs contract permission, a reason, and current criterion
- evidence; mtimes alone cannot prove or disprove success. Content identity does
- not establish semantic correctness or authorize a transitive scope expansion.
-
- ## Output contract
-
- The report must contain:
-
- - plan and policy references;
- - per-task role, status, evidence references, files changed, tests, and risks;
- - filtered or missing result records;
- - agreement that is supported by shared evidence;
- - contradictions and file conflicts;
- - recommended next action with explicit blockers.
-
- Write coordination output to the configured scratch area by default. Promote a
- report into a repository-owned evidence path only when the project explicitly
- requires a shipping artifact or acceptance record. Scratch output is not
- implicitly committable.
-
- ## Policy and context
+ # agent-output-reconciler (redirect)
- All numeric limits come from the canonical policy evaluated by
- `agent-collab policy evaluate`. Do not copy default budgets into the plan or
- this skill. Re-evaluate policy after a reconciliation cycle and before any new
- spawn. Obey the decision's scope: a v2 action stop forbids repeating that action,
- not safe primary-agent diagnosis; a goal stop preserves the hard gate. Persist
- a checkpoint before continuing. An eligible v2 slice advances automatically
- under the same goal, while v1 retains its original stopping behavior.
+ Merged into [agent-acceptance-gate](../agent-acceptance-gate/SKILL.md) in
+ 0.6.0. Run that skill: its "Step 1: Reconcile" is the former workflow, and the
+ report template moved to
+ [reconciliation_template.md](../agent-acceptance-gate/references/reconciliation_template.md).
- ## Safety rules
+ A plan that hands a round to the reconciler and then to the gate now needs one
+ gate pass. The rules are unchanged: missing and failed results stay distinct,
+ scope drift is recorded, and a reconciliation is not an acceptance decision.
- - Do not vote on factual truth. Prefer verified evidence and surface
- disagreement.
- - Do not hide failed or absent results with optimistic synthesis.
- - Do not paste raw logs when a path and bounded excerpt are sufficient.
- - Do not modify source files, canonical memory, history, or human decisions.
- - Do not commit, merge, push, or approve the round.
+ This stub is removed in 0.7.0. See [migration 0.6](../../docs/migration-0.6.md).