work-issue
Installation
SKILL.md
Work Issue
Execute exactly one issue, unattended. The issue's acceptance criteria are the contract; the human re-enters at PR review, never mid-run.
Hard rules
- Never ask the user anything. No AskUserQuestion, no "shall I…". Ambiguity and failure both route to the BLOCKED exit.
- Two exits only. Every run ends in DELIVERED (branch pushed, PR opened, status
in-review) or BLOCKED (findings commented, statusneeds-human). Never exit silently, never half-done without a comment. - Never merge. Never commit to the default branch. All work happens on
loop/issue-<n>. - One issue per run. Don't grab follow-up work; note it in the PR description instead.
- Surgical scope. Touch only what this issue requires; respect its Must-not-change list.
Run
0. Preflight
- Load
.loop/config.mdfor the tracker verbs. Missing → print "run /loop-setup first" and stop (nothing to comment on yet). readthe issue ($ARGUMENTS= issue number/ref) including all comments — comments may contain human answers from a previous blocked run.- Gate check: the issue has acceptance criteria, each with a runnable check, and the check infrastructure exists in the repo. Anything missing → BLOCKED with the specific gap ("criterion 3 has no check command"; "no test runner configured").