Reconcile

> Trace. On load, print first: =============== [lsa/skills/reconcile/SKILL.md] [lsa] ===============

LSA Reconcile (after — correctness)

See [CORE.md](../../CORE.md) §6 (the two checks). This is the after check; verify is the before check.

Role

Result verifier + spec maintainer.

Goal

Confirm the returned diff satisfies the spec; where reality diverged, the spec absorbs it.

Inputs

| Input | Source | |-------|--------| | The implementer's diff | delegate | | The spec + .feature files | specify | | Quality-gate checks (required input) | .lsa.yaml gate: — see [knowledge/quality-gate-contract.md](../../knowledge/quality-gate-contract.md). No gate: block → report the gate status NOT-RUNNABLE explicitly (Step 1); never silently skip. | | Scenario-run count N | .lsa.yaml reconcile.runs — default 3 when the key (or the file) is absent |

Steps

Three questions — does · only · all:

1. Does it work — run each Gherkin scenario against the diff N times, where N = .lsa.yaml reconcile.runs, default 3 when the key is absent (agents are stochastic); pass = succeeds on ≥95% of runs. At the default N = 3, ≥95% means all 3 runs pass (3/3); a 2/3 scenario fails. When reconcile.runs raises N for a high-stakes epic, pass stays ≥95% of runs (e.g. N = 20 → at least 19 passing). Then run the .lsa.yaml gate: block — required input, not an optional extra: run each configured check and cite its command + exit/output as the proof (the Rule 7 gate artifact). Run the block in one pass where the repo provides an aggregate runner (this repo: bash scripts/gate.sh, which reads the gate: block and prints each check's command + exit), and cite its consolidated output; absent a runner, run each configured command. If the repo has no gate: block, report the gate status explicitly as gate: NOT-RUNNABLE — no gate: block in .lsa.yaml in conformance.md and alongside the verdict — never silently skip the gate step. (→ scenario results + per-check gate results, or an explicit NOT-RUNNABLE gate status)
2. Only what's needed — every changed hunk traces to a requirement; an untraced hunk is over-delivery. Prove it by reading the Step-4 coverage table in reverse: every diff hunk appears in at least one requirement row; an orphan hunk (in the diff, in no row) is drift. (→ scope check)
3. All of the plan — every requirement (F1…, including non-scenario ones) maps to a change in the diff or a covering test; an uncovered requirement is under-delivery. Prove it with the Step-4 coverage table: a requirement row with no implementing hunk and no covering test is a failing row. (→ completeness check)
4. Write conformance.md around the requirement ↔ hunk coverage table — one row per requirement ID (F1…Fn from requirements.md) with four columns: requirement · the diff hunks/files that implement it · the scenario runs that prove it (e.g. 3/3) · a per-row verdict. Below the table, list any orphan hunks (drift, per Step 2) and the gate results (or the explicit NOT-RUNNABLE status, per Step 1). The judge cites this table — the only and all verdicts are read off it, not asserted in prose. Pass → done. Any check fails or the code diverged → present the drift (per [core/output](../../../core/skills/output/SKILL.md) Rule 7 Delivery test — never only in a subagent transcript or pre-tool-call text), take approval, and edit the spec in place to match reality. (→ verdict + conformance.md + any spec update)

Output

conformance.md — its core is the requirement ↔ hunk coverage table (one row per requirement ID: requirement · implementing diff hunks/files · proving scenario runs · verdict), followed by the orphan-hunk list (empty on PASS) and the per-check gate results (or an explicit gate: NOT-RUNNABLE — no gate: block in .lsa.yaml status) — + a verdict line reconcile: PASS @ — emitted as a distinct gate artifact in a context the implementer cannot author (see Constraints, Independence must be observable) — or a drift report + the spec updated to reality.

Coverage-table shape (synthetic):

| Req | Implementing hunks/files | Proving runs | Verdict |
|---|---|---|---|
| F1 | `src/status.ts` (new command) | `status.feature` Scenario 1 — 3/3 | ✅ |
| F2 | `README.md` §Usage | — (doc requirement, no scenario) | ✅ |

Orphan hunks: none.
Gate: lint ✓ (exit 0) · test ✓ (exit 0)   — or —   gate: NOT-RUNNABLE — no gate: block in .lsa.yaml

Constraints

• Run N times (N and the pass threshold per Step 1), never once. Check does · only · all — a passing-but-incomplete diff is not done. The spec absorbs reality — never revert the code, never silently accept a failing or uncovered scenario. Never silently skip the gate step — no gate: block means an explicit NOT-RUNNABLE gate status, not an omitted one.
• Independent grader. reconcile is the grader the work cannot edit: run it in a context with no write access to the tests, acceptance .feature scenarios, or quality-gate config (.lsa.yaml gate:) it grades; the implementer's diff never includes an edit to its own grader. (Reward-hacking defense — [knowledge/quality-gate-contract.md](../../knowledge/quality-gate-contract.md) §"Independence rule".)
• Never routed down. reconcile is a floored model-routing surface (lsa:reconcile) — it always resolves inherit, never a lower tier, even if .lsa.yaml routing: names one; grader quality is the safety floor of the whole system. Per [../../knowledge/model-routing.md](../../knowledge/model-routing.md).
• Independence must be observable, not asserted. The verdict (conformance.md + reconcile: PASS|FAIL @ , naming the SHA it graded) is authored in a separate context from the implementer and emitted in a commit separate from the implementation commit (or, where a single commit is unavoidable, as a record whose authoring context is provably not the implementer's); a run where reconcile is folded inline into the implementation commit fails this rule. Full rationale + the observed TripAnchor-1 failure: [knowledge/quality-gate-contract.md](../../knowledge/quality-gate-contract.md) §"Independence rule".

---

/lsa:reconcile — manual invocation. Also surfaced by the SessionStart drift hook.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: NVZver
• Source: NVZver/claude-marketplace
• License: MIT

Install and usage instructions live in the source repository linked above.