What problem does it solve? Long-running autonomous coding sessions tend to drift out of scope, touch protected hot paths, or silently widen into adjacent domains. This Skill keeps an agent executing bounded cleanup or build work overnight while preserving lane integrity and leaving a truthful control trail. ## Core Features & Use Cases - Bounded Lane Execution: Runs cleanup or build tranches only when the lane, hot-path exclusions, and stop conditions are already written down. - Structured Reporting: Requires every cycle to output the current lane, tranche completed, files changed, validation performed, residual risks, and the next bounded seam. - Explicit Stop Rules: Halts on unresolved ownership, path-coupling, or authority ambiguity instead of silently widening scope, and records the blocker in control docs. - Use Case: An operator decomposes a non-TUI cleanup into a safe lane, activates this mode overnight, and the agent iterates through tranches while updating the lane-owner control document and logging issues without touching TUI or dashboard hot paths. ## Quick Start Activate the dharma-autonomous-build mode and run the next bounded cleanup tranche defined in the overnight control document, reporting files changed and validation performed.