← ClaudeAtlas

hey-runlisted

Work through checklist items up to an agreed point in a loop, then report a summary. The user can name the scope; otherwise recommend one. Also recommends which items can run in parallel. Use on "take it from here", "run the loop", "handle these items", "how far can you get", "anything that can run in parallel".
keenkim1202/Hey · ★ 1 · Data & Documents · score 67
Install: claude install-skill keenkim1202/Hey
# Scoped loop Runs checklist items back to back. Real code changes, so **never start without an approved scope.** ```bash ROOT="${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}" # Codex names it PLUGIN_ROOT HEY="$ROOT/scripts/hey.py" ``` ## 1. Gather candidates and evidence ```bash python3 "$HEY" batch --limit 8 python3 "$HEY" next python3 "$HEY" dirty ``` `batch` supplies three mechanical signals. **Never decide on that output alone.** | Signal | Meaning | Limit | |---|---|---| | mentions first | the item body names another item | misses any dependency not written down | | overlap | backtick tokens (modules, files, types) are shared | misses the same file under a different name | | blocked | the item marks itself as waiting | misses anything not marked | So **read the actual code before fixing the scope.** Check which files each item would touch and whether the overlap verdict holds. Skipping that and running in parallel means they overwrite each other. If `dirty` shows uncommitted work, **do not start the loop.** Ask whether to clean up first. ## 2. Recommend a scope Use the user's scope if given. Otherwise recommend, on these four: - **Start where prerequisites are already closed.** Doing a later item first means redoing it when the earlier one lands - **Fit the hours remaining.** `AI 1.0` = 8 hours. Ask how much time is left and take that much - **End on something verifiable.** The scope boundary must be a point where build and tests pass - **Leave blocked items out.**