Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Agent Orchestration

Ralph loop yylo

Execute exactly one explicitly assigned YYLO Ledger task through the Ralph loop to a validated queued commit. Use only when the user explicitly requests ralph-loop-yylo.

Agentic Awesome SkillsLicense: MITAdded Sep 20, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Ralph loop yylo skill to help me with this.
SKILL.md3 files in this skill

Execute one assigned task in the Ralph loop

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

When to Use

  • The user explicitly requests ralph-loop-yylo for one already-assigned YYLO Ledger task.
  • You need to implement exactly that task through the validated loop to a queued, review-ready commit.

Limitations

  • Exactly one assigned task per run: never select unrelated work, broaden scope, push, deploy, merge, release, or mutate production.
  • Requires yy task start TASK_ID admission and yy task finish TASK_ID closure; stop after queueing - only the target owner runs yy merge land.
  • Docs-only import: the upstream scripts/kanban.sh wrapper is intentionally not bundled; references/ holds the worker contract.
  • Controller checkpoints are best-effort durability warnings, never lifecycle gates.

Example

yy task start TASK_ID
yy task preflight TASK_ID
yy task finish TASK_ID
Adapted from yylo-dev/yylo-skills (MIT) - v2.0.1; frontmatter, When to Use/Limitations, and safety boundaries added for upstream compliance. Docs-only import: scripts/kanban.sh runtime not bundled.