What problem does it solve? When the repository owner is unavailable, an agent must keep working without asking questions, avoid breaking shared files across parallel branches, and leave a clear record of every decision made overnight. ## Core Features & Use Cases - Chained branching: Each new task branches from the previous branch instead of main, preventing merge collisions in shared files like indexes and journals. - Written defaults instead of questions: Every decision that would have required the owner's input is recorded in the task folder with its reasoning and the cost of being wrong. - Morning list: A running table of completed work, branch names, verification commands, and postponed tasks is appended after each finished piece of work. - Use Case: The owner leaves for the night and asks for autonomous progress on the backlog; the agent works through tasks RT-12, RT-13, and RT-14 on a chained set of branches, records two defaults, postpones one task needing owner input, and hands over a merge-ordered morning list. ## Quick Start Tell the agent the owner is leaving and to run the autonomous-work pattern on the open task backlog overnight.
