AF write-adr
Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.
As a process F 63/100 · Will not run — References files that are not bundled: ../adr-decision-extraction/SKILL.md, ../adr-writing/SKILL.md
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
missing-refreference to a missing file: ../adr-decision-extraction/SKILL.md - warning
missing-refreference to a missing file: ../adr-writing/SKILL.md
Process rating: all ten parameters 63/100
- 0Tools and files. 2 referenced file(s) missing: ../adr-decision-extraction/SKILL.md, ../adr-writing/SKILL.md
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Steps. 26 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2224 tokens
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 491: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.