Work plans

Where they live

Work plans are created per branch in this location, not inside the repository.

~/.belloga/plans/{owner}/{repo}/{branch}/
├── requirements.md
├── design.md
└── tasks.md

{owner}/{repo} comes from the repository’s remote URL. Repositories without a remote use _local/{repository name}.

How they are filled in

1. When you create a worktree and pick a task type, requirements.md is pre-filled from that type’s template. An existing file is never overwritten.
2. When you start Claude Code in a Belloga terminal in that worktree, the plan hook tells it where the plan lives and how to write it.
3. Claude Code writes the three documents, asks you to review them, and then implements.
4. Once you confirm the work is done, it is told to move the plan folder under ~/.belloga/plans/done/.

Following progress

The worktree card shows the task type and tasks.md progress as a bar, such as “3/7 tasks done”. Only top-level checkboxes (- [ ], - [x]) in tasks.md are counted.

Click the plan on the card to open tasks.md, or design.md and then requirements.md if it doesn’t exist.

Plan panel

Expand a repository in Files mode to see a “Plans · repository name” panel above its file tree.

• Plans in progress show one row per branch, with task type and progress. Expand a row for the plan documents, and click one to open it.
• Plans moved under ~/.belloga/plans/deferred/ show in a collapsed Deferred group, and plans moved under ~/.belloga/plans/done/ in a collapsed Done group with their completion time.
• With no plans in progress it says “No plans in progress”. The list reloads as soon as the folders change.

Per repository

Work plans only work when the plan hook is on and the repository uses them. Turn them on or off per repository in the Agents tab of the settings, under Plan hook details → Per repository. Newly connected repositories are on.

In a repository that is off, creating a worktree doesn’t ask for a task type, and sessions get no plan guidance.