Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open notes/issues/, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before moving to the next. Sequential by default (one agent at a time) so changes never collide on shared files. Default scope is ALL open issues with a safety limit of 25; the user can widen the scope or raise the limit in their prompt. Pauses for the user only at genuine decision forks and before any paid generation or irreversible/outward-facing action. USE WHEN the user types /dev-loop, says "work through the issues", "run the dev loop", "grind the backlog", "implement all the open issues", "keep going through notes/issues until done", or after /dev-issues has filed a batch they now want executed. DO NOT FIRE for a single issue (just implement it), for content/video production, or when there are no open issues to execute. See body for ALSO FIRE / DO NOT FIRE / HARD INVARIANTS.
$npx -y skills add alecs5am/ralphy --skill dev-loopInstalls into the current project.
Run `npx skills use "https://github.com/alecs5am/ralphy" --skill "alecs5am/ralphy/dev-loop"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/alecs5am/ralphy" that are relevant to the current task. Run `npx skills add "https://github.com/alecs5am/ralphy"` and select the relevant skills, then follow their instructions.