decision-variance

Solid

Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report, mentions ADR conflicts, or asks which downstream artifacts the current state supports. Never decides alone — every arbitration is user-attributed and logged.

AI & Automation 137 stars 7 forks Updated today AGPL-3.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# decision-variance Reconcile the architectural artifacts against the scaffold; present variances; the user decides. This skill never arbitrates on its own — every recorded decision carries user attribution. The SMARTS lenses, cell rules, and strength labels are in `${CLAUDE_PLUGIN_ROOT}/includes/smarts/core.md` — read it before Phase 3. The append-only decision-log entry format is in `${CLAUDE_PLUGIN_ROOT}/includes/smarts/decision-log-format.md` — read it before writing a log line. ## Pre-flight Read these, or STOP and surface the gap — never guess a path or a position: - `<project-root>/.codearbiter/CONTEXT.md` — project context and the `stage:` maturity value. - `<project-root>/.codearbiter/security-controls.md` — only when a variance touches a security boundary (auth, crypto, secrets). Feeds the Securable lens. Locate the three architectural artifacts by **exact** filename — `01-architecture-breakdown.md`, `02-phased-build-plan.md`, `03-task-backlog.md` — first under `<project-root>/.codearbiter/plans/`, then the project root, then `docs/`. MUST NOT pattern-match similar names (`architecture-draft.md`, `task-list.md`); loose matching arbitrates against the wrong document. If any of the three cannot be located, ask the user for the path. Do not infer. ## Phase 1 — Locate inputs and detect stale decisions · gate: STOP Index, in addition to the three artifacts: - **Existing ADRs** — `<project-root>/.codearbiter/decisions/`. Record each by number, title, status, summ...

Details

Author
arbiterForge
Repository
arbiterForge/codeArbiter
Created
2 months ago
Last Updated
today
Language
Python
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

decision-lifecycle

Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only. Never authors an ADR as its own judgment — every ADR carries explicit user attribution.

137 Updated today
arbiterForge
Code & Development Listed

decisions-and-adrs

Use this skill whenever you create, write, modify, or statue an entry under `.decisions/` or `.adrs/`, or when you need to know the difference between a tactical DECISION and a strategic ADR, the two-zone frontmatter format of DECISION-NNN-*.md (zone author + zone review with `revisit`/`reviewed_by`/`reviewed_at`/`outcome` fields), the R2 strict rules under which green is allowed to author a tactical DECISION (scope=tactical, revisit=true at creation, necessary to unblock current task, DECISION-NNN referenced in code or commit message), or the R6 three-level defence around the `Authored-By:` commit trailer (pre-commit format, CI git-blame ↔ trailer cross-check, reviewer pass DoD sanity check). Also covers the architect's three statuing outcomes (confirm / reformulate / supersede) for tactical DECISIONS surfaced in RETRO.md `decisions_to_statue:` from the previous sprint, and the strategic ADR format. Loaded only by `architect` (writes strategic, statues tactical, both ADRs and DECISIONS), `green` (writes tact

0 Updated 5 days ago
JLugagne
AI & Automation Listed

architecture-decisions

Use when structural code choices need durable rationale: ADRs, tradeoffs, consequences, reversibility, ownership, review triggers, and validation plans.

8 Updated today
Xopoko