AF Living ADR
Living Architecture Decision Records — automatically draft, number, and update ADRs from git diffs, PR descriptions, or plain-English decisions. Detects architectural signals in code changes (new database tables, new auth methods, new external integrations, framework changes) and drafts a pre-filled ADR in the RFC 822 / Nygard format. Also marks existing ADRs as "Superseded" when new decisions replace them. Outputs to docs/adr/ with sequential ADR-NNN numbering. Zero external API — works entirely from your codebase and git history. Triggers on "write ADR", "document this decision", "architecture decision", "new ADR", "living adr", "/living-adr".
As a process F 51/100 · Will not run — References files that are not bundled: ADR-${NEXT_NUM}-${SLUG}.md, $fname
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: ADR-${NEXT_NUM}-${SLUG}.md - warning
missing-refreference to a missing file: $fname - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: ADR-${NEXT_NUM}-${SLUG}.md, $fname
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (Living ADR) differs from the folder (phy-living-adr)
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 2704 tokens
- 100Running it twice. Mutating operations check current state
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 653: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.