The Rule Was on the Other Branch
Every team I have worked with keeps its practices in a dozen places. The PR checklist lives in one repository. Who promotes to production is on a wiki page for the whole organisation. The branch a project integrates into is a convention of that project. The test command is in a README, unless it moved to a Makefile. And a good part of it lives only in the heads of the people who have been there…
The new software delivery-loop plugin for Claude Code and Codex streamlines the process of taking a task from its ticket to a verified test environment and final production handover. Instead of keeping practices scattered across various locations, the plugin consolidates them into profiles that mirror the structures of each organization and project.
The plugin manages ten phases of a task, from understanding the work to building, testing, proving changes, and finally handing over to production. Each phase relies on practices specific to the organization or project, which are defined in profiles at different levels. The shared profiles, containing universally applicable rules, are stored in a private repository and applied across multiple repos.
When a rule changes, it's updated in the relevant profile through a single pull request, ensuring all users get the latest version upon the next installation. Profiles are rechecked at the start of each task to ensure they remain current, preventing stale practices from persisting. The result is an efficient, organization-wide workflow that adapts to each environment without the need for manual setup or ongoing maintenance.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.