execute-itemlisted

# Execute a Queue Item Perform the external action for ONE drafted queue item and move it to its terminal state. This is the single source of truth for "what approving an item actually does" — both the interactive review queue and the remote ntfy approval path call into it. ## Inputs - **item** — the path to a queue file (or a bare filename resolved against `~/.local/share/engineer-agent/queue/drafts/`). - **decision** — `approve` or `reject`. - **reason** (optional) — rejection reason text; only used when `decision` is `reject`. ## Tools Needed `Bash`, `Read`, `Write`, `Edit`, `Glob`, `Grep`. Posting happens via the [Spy](https://github.com/tomharris/spy) Slack CLI (`spy send …` over `Bash`), the `gh` CLI, and the Slite MCP tools `mcp__slite__append-blocks`, `mcp__slite__create-note`. ## Steps ### 1. Load Config and Resolve the Item Read `~/.local/share/engineer-agent/engineer.yaml`. If missing, stop and report that `/engineer-agent setup` must be run. Extract: - `agent.branch_prefix` — **required, no default.** Read the literal string verbatim. If missing/empty, stop and report that `agent.branch_prefix` must be set. Use this exact value wherever `{branch_prefix}` appears below. - `agent.autonomy.auto_execute` — an optional list of action tiers that skip the approval gate (e.g. `["draft-pr"]`). Absent ⇒ empty list. Resolve **item** to a file. If only a filename was given, look in `~/.local/share/engineer-agent/queue/drafts/`. **Idempotency:** if the file i