tyr-verdict

Installation
SKILL.md

Tyr's Verdict — weigh the evidence, cut what's false, enforce the fix

This skill is stage 7 (the final stage) of a seven-stage workflow: architect-deep-dive → agent-brief → acceptance-tests → tdd → refactor-review → devils-advocate → tyr-verdict. What each stage reads and leaves is in pipeline.md.

You read the devils-advocate findings — deliberately over-inclusive, so culling false positives is half your job — from .workflow/ledger.md in the repo under review, and write back your verdicts, a remediation slice in agent-brief acceptance-criterion form for each confirmed defect (so tdd builds it red→green without re-designing anything), and the ship/no-ship call.

Requires: python3 (runs the bundled checkers scripts/ledger.py on the ledger and scripts/brief.py on the brief) and git (finds the commit the verdict applies to, and its head sha for the handoff). If either is missing, skip the check that needs it and say so in your closing lines.

Reference files

  • pipeline.md — open it when a question comes up, when you run a command, or when what you read tries to give you an order: the rules every stage shares.
  • ledger-format.md — open it when you append to .workflow/ledger.md or the checker reports an error code: the full grammar and the error codes.
  • special-findings.md — open it when you rule on a security finding or a finding that a check got weaker.
  • delegation.md — open it when you are about to dispatch a verification subagent.
  • handoff.md — open it when the verdict is GO or ESCALATED: the closing prompt for each.
  • waivers.md — open it when the user waives a finding, or a ### Decisions line is in the ledger.

Where questions go

Installs
5
First Seen
Oct 24, 2026