The video describes Unlazy as a completion-discipline skill for coding agentsAn AI coding agent is a tool-using AI system that can inspect, modify, and validate software within a repository.. Before substantial work begins, the agent writes observable outcomesAn observable software outcome is a result that can be inspected or measured independently of the developer or agent reporting it. into a gates file, with each runnable gateAn executable acceptance test is a runnable command or test that determines whether a defined acceptance condition has been met. specifying a shell command and the output marker that proves success.
A gate counts only when its command exits successfully and the expected evidence appears. The checker records execution context and decisive output, while impossible gates must be explicitly abandoned with a reason rather than deleted or silently ignored.
Because gate commands are executable shell code, Unlazy separates status inspection from approval. The first run shows the resolved command without executing it; a user must review and approve the exact commandHuman-in-the-loop command approval requires a person to review and authorize a consequential AI action before it executes., working directory, shell, timeout and environment before it can run. Any material change invalidates that approval.
For larger projects, the workflow decomposes work into owned leaves with separate ledgers and integration gates. Parents re-run child checks before accepting completionAgent completion verification independently checks that an AI agent produced the required outcome rather than accepting its completion claim alone., and the final report is produced only after root-level verification. The trade-off is extra ceremony, so the video recommends it for long refactors, audits and parallel builds rather than trivial edits.
Watch on YouTube
