decision-lifecycle
SolidAuthor 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.
Install
Quality Score: 80/100
Skill Content
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
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
ca-adr
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
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.