decisions-and-adrslisted

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
JLugagne/claude-skills · ★ 0 · Code & Development · score 72

Install: claude install-skill JLugagne/claude-skills

# Decisions and ADRs The decision log mechanism for the agile-team-v2 workflow. Two distinct stores — `.decisions/` for tactical/strategic decisions with a review lifecycle, `.adrs/` for strategic Architecture Decision Records — plus the `Authored-By:` commit trailer that audits write authority. This skill is loaded only by the three agents that **write** to these stores: architect, green, sprint-planner. Other agents read DECISION/ADR files freely (they're public artifacts), but they don't need the format details, the R2 strict rules, or the statuing protocol. --- ## The two stores ### `.adrs/` — strategic, multi-feature, project-direction Architecture Decision Records. Format unchanged from v1. Strategic only — multi-feature impact, invariant changes, contracts that other features will depend on. The architect writes ADRs. ```markdown # ADR <NNN> — <short title> Date: <YYYY-MM-DD> Scope: strategic Author: architect Decided: [autonomously | with human input] Revisit: [true | false] ## Context ## Decision ## Consequences ## Related - Features: <links> - Prior ADRs: <links or None> - Superseded ADRs: <links or None> ``` `Revisit: true` indicates an autonomous decision under uncertainty — picked up at retro for human review. Tactical decisions go to `.decisions/`, **not** `.adrs/`. Do not mix. ### `.decisions/` — tactical or strategic, with two-zone frontmatter and review lifecycle The decision log distinct from strategic ADRs. The architect writes strategic DECISI