guild-loop-implement

Coordinate multi-layer adversarial loops across a lane's delivery lifecycle.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill guild-loop-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guild-loop-implement
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/loop-implement
Command: npx skills add https://github.com/lookatitude/guild --skill guild-loop-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates multi-layer adversarial loops across a lane's delivery lifecycle to validate plans against targeted challengers and structured audit trails.

Core Features & Use Cases

  • Supports L3, L4, and security-review loops with per-lane isolation and per-lane restart handling.
  • Integrates with guild:execute-plan to orchestrate nested dialogues, sentinel termination, and cap-aware progress.
  • Provides deterministic restart flow, plan validation constraints, and handoff receipts for auditability across restarts and lanes.

Quick Start

Enable the loop-implement skill by setting loops_applicable on a lane and running the guild workflow to start nested L3/L4/security-review loops.

Frequently Asked Questions about guild-loop-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate adversarial loops across multiple delivery lanes?

To validate plans against challengers, the skill coordinates multi-layer adversarial loops across a lane's delivery lifecycle, managing L3, L4, and security-review interactions with per-lane isolation and structured audit trails.

How do I handle restarts and audit trails during adversarial loop execution?

Adversarial loop execution manages restarts via deterministic restart logic and per-lane counters, providing handoff receipts and emitting structured JSONL events to maintain a reliable audit trail across restarts.

What triggers the adversarial validation loops in a delivery pipeline?

Adversarial validation loops are triggered when a lane activates the loops feature via --loops flags set to implementation or all, applying plan validation constraints and delegating interactions to specialized challengers.

How does the lane workflow integrate with execute-plan for nested dialogues?

The lane workflow delegates nested dialogues, sentinel termination detection, and cap-aware progress management to the execute-plan component, ensuring structured plan validation and escalation prompts across isolated lanes.

What are the limitations of running multi-layer adversarial loops?

Running multi-layer adversarial loops requires explicit activation via --loops flags and depends on specialized challengers, meaning loops will not execute automatically without proper lane configuration and per-lane isolation setup.