What problem does it solve? Turning a forge issue into a reviewed, merged, and deployed feature normally requires manual coordination across coding, review, merge, and verification steps. This Skill encodes the boucle protocol so an agent can drive that entire loop autonomously on GitLab or GitHub CI, with the human intervening only at spec-approval and MR-approval gates. ## Core Features & Use Cases - Label-driven state machine: Issues move through triage, worker, reviewer, merge, deploy, and e2e stages via boucle: labels, with SHA-anchored verdicts and marker-stamped comments preventing self-trigger loops. - Forge-agnostic operation: A forge abstraction layer (bin/forge/gitlab.sh, bin/forge/github.sh) lets the same loop run on GitLab CI or GitHub Actions, including mono-user mode without a separate bot account. - Self-healing and self-improvement: A scheduled doctor sweep recovers stuck issues, and a LESSONS.yml admission workflow captures reusable lessons from failed iterations. - Use Case: A product builder opens an issue describing a UI change, adds the boucle:triage label, and the loop triages it, implements on a worker branch, deploys a preview, runs adversarial review, merges after a thumbs-up, and verifies production with a SHA-anchored e2e gate. ## Quick Start Add the boucle:triage label to a forge issue and assign it to the bot so the loop triages, implements, reviews, merges, deploys, and verifies the feature end to end.