Slash Command

/apply-verdict

Deterministically apply a reviewer's verdict — tick Acceptance Criteria, stamp the Verdict section, move the task to its new state

Popularity

Parent stars

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/delivery-team:apply-verdict

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Apply a reviewer verdict to a task. This is the **bookkeeping half** of the
review gate: the reviewer agent JUDGES (read-only) and returns a structured
verdict; this command APPLIES it deterministically so nothing depends on an
agent remembering to tick a box (see `.claude/rules/workflow.md` and
`docs/foundation/README.md` — judgment vs bookkeeping).

Arguments: **$ARGUMENTS** — at minimum a task id and a verdict.

Run the script (never hand-edit the checkboxes or the state move yourself):



Rules:
- `--verdict approve` ticks **all** Acceptance Criteria by default and moves the task to `wo...

Command Content

26 lines · ~417 tokens

Stats

LanguageJavaScript

Parent stars1

MaintenanceExcellent

Last CommitJun 16, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Tags

Apply a reviewer verdict to a task. This is the bookkeeping half of the review gate: the reviewer agent JUDGES (read-only) and returns a structured verdict; this command APPLIES it deterministically so nothing depends on an agent remembering to tick a box (see .claude/rules/workflow.md and docs/foundation/README.md — judgment vs bookkeeping).

Arguments: $ARGUMENTS — at minimum a task id and a verdict.

Run the script (never hand-edit the checkboxes or the state move yourself):

node .claude/scripts/apply-verdict.mjs --task <TASK-NNN> --verdict <approve|changes-requested> \
  [--ac all|<comma-separated 1-based indices>] [--note "<one line>"] [--blocking "item1;item2"]

Rules:

--verdict approve ticks all Acceptance Criteria by default and moves the task to work/done/. Pass --ac 1,3,4 only if the reviewer confirmed a subset (the rest stay unticked → the gate will then refuse done/, which is correct).
--verdict changes-requested ticks nothing by default and moves the task to work/review/. Pass --blocking "..." with the required fixes.
The script also syncs the task's state cell in work/ROADMAP.md and writes a dated Reviewer (Opus) verdict Log entry. It does not commit — review the diff, then commit (the husky gate validates done/ on commit).

After it runs, relay: the verdict, how many Acceptance Criteria were ticked, and the new state. If changes-requested, summarize the blocking items and offer to re-dispatch the owning implementer.