decision-variance

Compare architectural artifacts against the scaffold and label variances as concur, divergent, or silent.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill decision-variance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-variance
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/decision-variance
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill decision-variance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reconcile architectural documents with the actual scaffold so contradictions, stale decisions, and missing implementation evidence do not slip through unnoticed.

Core Features & Use Cases

  • Variance Detection: Compares the project’s architectural artifacts against the scaffold and labels each decision as concur, divergent, or silent.
  • SMARTS Arbitration Support: Structures each meaningful variance into a decision-ready analysis so the user can review tradeoffs instead of guessing.
  • Decision Logging: Preserves an append-only record of user-attributed resolutions and checks for stale prior decisions before new variances are added.
  • Downstream Readiness Review: Assesses which follow-on artifacts are ready, partial, or blocked based on the current decision state.
  • Use Case: A team updates implementation files after an ADR changes and uses this Skill to identify mismatches, surface the affected decisions, and capture the user’s chosen resolution in the log.

Quick Start

Ask the decision-variance skill to compare the project’s architectural artifacts against the current scaffold and report every variance that needs your review.

Frequently Asked Questions about decision-variance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect architectural drift between my ADRs and project scaffold?

Detect architectural drift by comparing decision logs against the current scaffold to surface variances. The analysis labels each architectural decision as concur, divergent, or silent based on exact filename matching.

What is SMARTS-based variance analysis for architectural decisions?

SMARTS-based variance analysis structures architectural conflicts into a decision-ready format for user arbitration. It surfaces tradeoffs for divergent or silent decisions so users can review impacts without guessing.

How do I check for stale decisions in an append-only decision log?

Check for stale decisions by auditing the append-only decision log before adding new variances. The reconciliation process identifies outdated architectural artifacts and preserves user-attributed resolutions without silently resolving conflicts.

Can I assess downstream artifact readiness after resolving ADR conflicts?

Yes, you can assess downstream artifact readiness after resolving ADR conflicts. The review evaluates follow-on artifacts and labels them as ready, partial, or blocked based on the current decision state.

Does decision variance arbitration work without exact filename matching?

No, decision variance arbitration requires exact filename matching to function correctly. The reconciliation process relies on precise artifact identification to compare architectural documents against the scaffold.

Why does my architectural decision log show silent variances after a scaffold update?

Silent variances appear when an ADR changes but implementation files are not updated to reflect the new architectural decisions. The variance detection compares the artifacts and flags missing implementation evidence as silent.