How do I install the Ca Reconcile skill?

Run npx skillmds@latest add majiayu000/ca-reconcile-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ca Reconcile safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ca Reconcile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ca Reconcile free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ca Reconcile?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ca Reconcile by majiayu000 — Agent Skill

Name: Ca Reconcile
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

$ca-reconcile — architectural arbitration

Reconciles the project's architectural artifacts against the scaffold and prior decisions, or challenges a specific ADR that is wrong, stale, or in conflict with another. Presents SMARTS analyses and recommendations but never arbitrates — every variance is resolved by an explicit user choice recorded in the decision log with user attribution. With no argument it runs a full reconciliation pass; an argument scopes it to a named ADR, conflict, or artifact.

Routes to

The decision-variance skill (${CLAUDE_PLUGIN_ROOT}/routines/decision-variance/SKILL.md). It locates the three architectural artifacts by exact filename — 01-architecture-breakdown.md, 02-phased-build-plan.md, 03-task-backlog.md (under <project-root>/.codearbiter/plans/) — and indexes the append-only decision log at <project-root>/.codearbiter/decisions/decision-log.md. It MAY dispatch the decision-challenger agent (${CLAUDE_PLUGIN_ROOT}/agents/decision-challenger.md) to stress-test an in-scope ADR — optional, not forced. Each variance ends in one of three user-chosen outcomes:

Ratify — the existing decision stands; the SMARTS analysis and re-affirmation are logged.
Supersede — a new decision is recorded by appending a log entry whose Supersedes: references the prior one; a replacement ADR is authored via $ca-adr.
Surface as [CONFIRM-NN] — unresolvable now; a numbered placeholder is added to <project-root>/.codearbiter/open-questions.md.

When NOT to use

Author a brand-new ADR with no prior conflict → $ca-adr.
Check ADR health (aged, unchallenged, unresolved CONFIRM-NN) → $ca-adr-status.
A general architectural discussion without recording a decision → $ca-btw.
A rule conflict between project docs and code → $ca-conflict.
Routine git text-merge conflicts — this is architectural reconciliation, not merge resolution.

Hard gate

MUST NOT record an arbitration decision without an explicit user choice; decline "you decide" / "use your best judgment" with a structural refusal (the only delegation is the user verbatim accepting the recommendation, logged as such in Decided by:). MUST match the three artifacts by exact filename. The decision log is append-only — MUST NOT edit or rebuild a prior entry; supersede by appending. MUST NOT modify the artifacts, scaffold, or code to "fix" a variance. MUST NOT author an ADR as the disposition of a routine finding — ADRs are authored only via $ca-adr with user attribution.

---name: ca-reconcile-2description: SMARTS arbitration — reconcile architectural artifacts against the scaffold and prior decisions; every variance resolved by an explicit, user-attributed choice.---# $ca-reconcile — architectural arbitrationReconciles the project's architectural artifacts against the scaffold and prior decisions, or challenges a specific ADR that is wrong, stale, or in conflict with another. Presents SMARTS analyses and recommendations but never arbitrates — every variance is resolved by an explicit user choice recorded in the decision log with user attribution. With no argument it runs a full reconciliation pass; an argument scopes it to a named ADR, conflict, or artifact.## Routes toThe `decision-variance` skill (`${CLAUDE_PLUGIN_ROOT}/routines/decision-variance/SKILL.md`). It locatesthe three architectural artifacts by exact filename — `01-architecture-breakdown.md`,`02-phased-build-plan.md`, `03-task-backlog.md` (under `<project-root>/.codearbiter/plans/`) —and indexes the append-only decision log at`<project-root>/.codearbiter/decisions/decision-log.md`. It MAY dispatch the`decision-challenger` agent (`${CLAUDE_PLUGIN_ROOT}/agents/decision-challenger.md`) to stress-test anin-scope ADR — optional, not forced. Each variance ends in one of three user-chosen outcomes:1. **Ratify** — the existing decision stands; the SMARTS analysis and re-affirmation are logged.2. **Supersede** — a new decision is recorded by appending a log entry whose `Supersedes:` references the prior one; a replacement ADR is authored via `$ca-adr`.3. **Surface as `[CONFIRM-NN]`** — unresolvable now; a numbered placeholder is added to `<project-root>/.codearbiter/open-questions.md`.## When NOT to use- Author a brand-new ADR with no prior conflict → `$ca-adr`.- Check ADR health (aged, unchallenged, unresolved CONFIRM-NN) → `$ca-adr-status`.- A general architectural discussion without recording a decision → `$ca-btw`.- A rule conflict between project docs and code → `$ca-conflict`.- Routine git text-merge conflicts — this is architectural reconciliation, not merge resolution.## Hard gateMUST NOT record an arbitration decision without an explicit user choice; decline "you decide" /"use your best judgment" with a structural refusal (the only delegation is the user verbatim acceptingthe recommendation, logged as such in `Decided by:`). MUST match the three artifacts by exactfilename. The decision log is append-only — MUST NOT edit or rebuild a prior entry; supersede byappending. MUST NOT modify the artifacts, scaffold, or code to "fix" a variance. MUST NOT author anADR as the disposition of a routine finding — ADRs are authored only via `$ca-adr` with userattribution.

Frequently asked questions

Ca Reconcile