runlisted

# kagura-engineer: run Thin wrapper around the `kagura-engineer run` CLI verb. It drives one GitHub issue through the full memory-grounded loop to an open PR. It reimplements nothing — the orchestration lives entirely in the CLI; this skill discovers config, gates on `doctor`, shells out, and surfaces the result. > ⚠️ **This is a Harness, not an atomic tool.** Before launching, make sure the user > understands the consequences and has confirmed: > - **Repo mutation** — creates a `run-<issue>` git worktree and commits there. > - **PR creation** — opens a GitHub pull request via gh-issue-driven on success. > - **Cost** — invokes `claude -p` multiple times (start / implement / ship). > - **HITL** — gates can halt (`blocked`, exit 2) and wait for a human decision. **Announce:** "Using the kagura-engineer:run skill — this is a Harness that will create a PR." ## No-argument usage If invoked without an issue number, do NOT guess or shell out — print this and stop: ``` kagura-engineer:run <issue-number> Drive one GitHub issue to a PR via the kagura-engineer harness. ⚠ Harness: creates a worktree + commits, opens a PR, spends model budget, gates on HITL. Example: kagura-engineer:run 42 New here? run kagura-engineer:doctor first to check the environment. ``` ## Steps 1. **Validate the issue argument.** The CLI takes a single positive integer issue number. Reject anything that does not match `^[1-9][0-9]{0,8}$` before interpolating it into the shell — do not pass