critiquelisted

# /forged:critique Critique the native Bead before execution. The goal is one useful adversarial pass proportional to risk, not a review treadmill. This skill reads and comments on operator-scoped Beads; it does not edit their normative spec fields and does not launch Forged. ## Load the authoritative record ```bash export ANVIL_HOME="${ANVIL_HOME:-$HOME/.anvil}" export BEADS_DIR="${BEADS_DIR:-$ANVIL_HOME/beads}" BD_BIN="${BD_BIN:-$(command -v bd)}" env BEADS_DIR="$BEADS_DIR" "$BD_BIN" show "$BEAD_ID" \ --long --include-comments --json ``` Read title, `description`, `design`, `acceptance_criteria`, `notes`, type, status, `metadata.repository`, parent and dependency edges. Inspect the target repository named by the metadata read-only. Do not substitute a sidecar file, conversation summary, or repository-local Beads store. If required native fields are absent, repository metadata is missing or wrong, or an unchecked question remains, report that blocking defect and stop. The record is not eligible for critique-as-approval. ## Choose the smallest useful topology - **Low risk:** the lead agent performs one structured critic pass. - **Normal risk:** delegate one independent critic using `../../agents/critic.md` relative to this skill, then verify and synthesize its findings. - **High risk:** use a small cross-family panel only when security, data loss, concurrency, compatibility, or a multi-slice contract warrants distinct perspectives. Use the host's native dele