tcashel

Activates when reviewing a Forge-launched pull request. Reads the PR diff, compares it against the original Forge spec when one is available, and produces a structured review verdict the user (or downstream automation) can act on. Use when the user asks to review, score, or check whether a Forge PR is mergeable.

Activates when an operator selects review items (Forge findings, inline comments, and/or review summaries) in the Forge review UI and clicks 'Fix N selected'. Validates each selected target against the current code, then surgically fixes only the targets judged valid. Used by the forge __comment-fix-worker pipeline.

Activates when the user wants to turn an idea or a plan-mode plan into a Forge task spec — research the repo, draft in the Forge schema, then persist via `forge spec save`. Use when the user says they want to run something with Forge, when they've just produced a plan they want to ship to a coding agent, or when they explicitly invoke /forge-ship-plan.

Applies a curated subset of synthesizer recommendations to a Forge spec body. Invoked programmatically by the auto-improve orchestrator after `forge spec save`; not auto-activated.

Adversarial critique of a Forge task spec. Identifies vague acceptance criteria, undefined behavior, contradictions, missing edge cases, scope creep, and assumptions deferred to the implementing agent. Produces a structured findings list with severity labels.

Activates during the forge auto-fix loop after a reviewer returns request-changes. Reads the review findings, reads the spec, and surgically fixes BLOCKER and HIGH severity issues only. Used by the forge runner after a reviewer verdict of request-changes.

Synthesizes two independent spec critiques into a single prioritized recommendations document. Classifies findings as corroborated, single-critic-only, or conflicting, and proposes concrete spec edits the user can selectively apply.

Runs the two-critic panel over a spec. Invoke when the user wants a spec reviewed, critiqued, or hardened before execution. Dispatches two independent critics, synthesizes their findings into a prioritized recommendations document, and surfaces conflicts plus open questions for the user to adjudicate. Entry point for the plan -> critique -> adjudicate flow.

Pull the beads ready-frontier (bd ready, honoring $BEADS_DIR) and run the headless execute -> quality gate -> draft PR -> review -> one auto-fix round loop over the chosen issue(s). Glue around the execute-review-fix workflow. Use after /anvil:adjudicate has locked specs into bd issues and you want them built. Stops at draft PRs for human adjudication; never merges.

Activates when the operator wants to turn an idea — or a plan-mode plan they just produced — into a locked anvil spec. Collaborate in plan mode to draft a self-contained spec in the anvil schema, write the body to ~/.anvil/specs/<id>.md, create a matching beads issue so it joins the ready-frontier, and enforce the open-questions lock gate before it can be marked ready. Use when the operator says they want to run something through anvil, when they've just produced a plan to ship to a coding agent, or when they invoke /anvil:plan.

Walks the operator through every unresolved CRUX in an anvil-spec-recommendations document one at a time — conflicting critic findings and open questions — captures the resolution, writes it back into the spec body at ~/.anvil/specs/<id>.md, and gates: the spec cannot leave adjudication with any crux unresolved. When clean, flips the bd issue to ready.

One-time setup for anvil: install and configure beads (bd or br) operator-scoped, verify the table-stakes tooling (git, gh + auth, claude), stand up the out-of-repo state under ~/.anvil, and PROVE the install imposed nothing on any target repo. Use when the operator first installs the anvil plugin, when bd/br is missing, or when /anvil:plan or /anvil:dispatch complains that beads isn't set up.