ralph-loop

Solid

Execute exactly one explicitly assigned Kanban task to a validated queued commit. Use only when the user explicitly requests ralph-loop.

AI & Automation 59 stars 6 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
59
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
43
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Read [references/implement.md](references/implement.md) completely and follow it. Stay within the assigned task. Do not select unrelated work, edit `tasks.md`, auto-tag releases, push, deploy, mutate production, or broaden scope because another issue is noticed. Record a bounded related Kanban follow-up when necessary. Keep durable instructions concise and evidence-backed. Status belongs in the task response and runtime receipts, not `AGENTS.md`. Controller checkpoints are best-effort local durability warnings after terminal metadata is durable. They never gate `yy pi`, `yy task`, `yy merge`, product commits, candidates, or releases. ## Complete assigned request Treat the following as the complete user-assigned request. Preserve task references and directives literally; resolve them only through the normal agent workflow. $ARGUMENTS

Details

Author
yylo-dev
Repository
yylo-dev/yylo
Created
8 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category