decision-lifecycle

Solid

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.

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-lifecycle Author and track ADRs. Routed to when the user invokes `/adr "<title>"` (author a new ADR) or `/adr-status [--adr N]` (list ADR health, read-only). Every ADR is user-attributed — this skill never records a decision the user did not explicitly make. The append-only decision-log format (entry fields, supersession protocol) lives in `${CLAUDE_PLUGIN_ROOT}/includes/smarts/decision-log-format.md`. Read it before writing a log line; do not restate it here. **Boundary with `decision-variance`.** This skill owns ADR *authoring* and *status* (`/adr`, `/adr-status`) — recording a decision the user has already made, and reporting ADR health. `decision-variance` owns *arbitration* — detecting variances between artifacts and the scaffold, scoring options via SMARTS, and the decision log itself. The two share the canonical SMARTS reference under `${CLAUDE_PLUGIN_ROOT}/includes/smarts/` (`core.md` for scoring, `decision-log-format.md` for the log) and one ADR template (`references/adr-template.md`); they are one domain split by responsibility, not duplicated. When a decision needs *making* (competing options), route to `decision-variance`; when it needs *recording* (already decided), stay here. ## Pre-flight Read these, or STOP and surface the gap — never guess a path: - `<project-root>/.codearbiter/decisions/` — the ADR directory and existing records. Create it on first `/adr` if absent. - For `/adr`: confirm the user explicitly authorized this decision and suppl...

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

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 Solid

ca-adr

Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.

137 Updated today
arbiterForge
Code & Development Listed

decision-records

Create, review, update, supersede, and audit Architecture Decision Records (ADRs) for durable project decisions. Use when a user asks for an ADR, decision log, architecture decision, design decision, communication or brand voice decision, or recorded rationale; when a cross-cutting technical, product, design, content, marketing, security, operational, or process choice must remain understandable across people, tools, and agent sessions; or when another skill identifies a decision whose undocumented rationale would otherwise drift. Preserve existing repository conventions and do not create skill-specific dot folders or private memory formats.

0 Updated 2 days ago
sebastian-software