run-feature
Installation
SKILL.md
Take a feature whose decision record is committed all the way to a ready PR with one kick.
The loop is scripts/run.mjs, which sits next to this file: a zero-dependency Node script that creates a worktree on slices/<slug>, writes a missing spec or slices file headlessly first, runs one fresh headless harness session per slice, and reads progress only from git trailers and the slices file.
Steps
- Find the slug: the one given, or the only feature folder under
spec/features/, or ask. The target repo is the current project unless the user names another. - Check the input:
spec/features/<slug>/decisions.md, or an already writtenspec.md, is committed. With both missing, tell the user to settle the decisions first and end the turn. - Kick the run: from the target repo's root, run
node <skill-folder>/scripts/run.mjs <slug>, resolving the script's full path from this skill's folder, and stream its output. Add--on-hostonly when the user asked to run on this machine; without it the script refuses, and that refusal is the end state to report. Add--agent-accountwhen the daemon's sessions spend the separate agent account, as on the VM, so the run keeps that account's reserve. When the target repo's own checkout is sitting onslices/<slug>with a clean tree, switch it back to the default branch first; the script refuses to run while any checkout holds the branch. Do not parse the harness sessions' output for state; the script already decides from git alone. - Report the end state: the exit code, the slices landed, the worktree path, the PR, and whether it ran with
--on-hostand--agent-account.