Skip to content

Fix yolo linked-branch timing and branch recovery in plan-lifecycle #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DocksDocks merged 1 commit into from
Oct 19, 2026
Merged

Fix yolo linked-branch timing and branch recovery in plan-lifecycle #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion plugins/plan-lifecycle/skills/productivity/plan-manager/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ user-invocable: true
metadata:
pattern: tool-wrapper
updated: "2026-10-19"
content_hash: "39f14e113d57bf289cff3e5c82d7afabba0d2a67477b1f02dc23bead8152e5e5"
content_hash: "243b9e9f8f3a8755b28f902d400f4e0de2bf40f46d42ea6a4530e44f2ec5d6d8"
---

# Plan Manager
Expand Down
7 changes: 4 additions & 3 deletions ...ins/plan-lifecycle/skills/productivity/plan-manager/references/plan-contract.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,14 +262,14 @@ reserved label namespace: <label>

### Linked branch

Set up the linked branch after the plan is ongoing and before any code change:
Set up the linked branch after the plan is ongoing and before any code change.
A yolo run uses the timing and worktree rules in Yolo runs instead.

1. Run `git status --porcelain`. Continue only when it prints nothing. Never
stash, move, or commit ambient work to make it clean.
2. If the checkout is dirty, use a separate clean worktree only when the user
approves it in this session through `ask`. Otherwise block the plan and
report the dirty paths. A yolo run uses the worktree rule in Yolo runs
instead.
report the dirty paths.
3. Run `gh issue develop <n> --list --repo <owner/repo>`. Reuse a listed branch.
4. If no branch is listed, run
`gh issue develop <n> --repo <owner/repo> --base <default> --checkout`.
Expand Down Expand Up @@ -338,6 +338,7 @@ question. All other contract rules stay in force.
|---|---|
| Path and Mode | Plan with `Mode: plan-and-implement` |
| Non-local Effect step before the landing merge | The effect table below |
| Linked-branch timing | Right after `new`, while the plan is drafting |
| Dirty checkout at linked-branch setup | A separate clean worktree, without a question |
| Review-loop continuation | The round ceiling below |
| Plan-review `blocked` verdict | The manager decides with evidence |
Expand Down
10 changes: 5 additions & 5 deletions plugins/plan-lifecycle/skills/productivity/yolo/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ disable-model-invocation: true
metadata:
pattern: pipeline
updated: "2026-10-19"
content_hash: "e80d15cf90e21f7cbd05093c90b0936d7c8558b420bf28c814cb53b59e9f7e48"
content_hash: "60d809dee20db8430222e943110dbff3e144540bd5655de8bb90fe62bf878be0"
---

# Yolo
Expand Down Expand Up @@ -218,10 +218,10 @@ Open findings: <MEDIUM or LOW findings left at the ceiling, or none>.

The issue is the run record. Run `show <n>` for the status and verdicts. Run
`gh issue develop <n> --list --repo <owner/repo>` for the branch. After the pull
request exists, GitHub lists no branch there. Then run
`gh issue view <n> --repo <owner/repo> --json closedByPullRequestsReferences`
and read the pull request head. Run `git worktree list` for a worktree. Count
review rounds from issue comments.
request exists, GitHub lists no branch there. Then read the pull request number
from `gh issue view <n> --repo <owner/repo> --json closedByPullRequestsReferences`,
and read the branch from `gh pr view <pr> --repo <owner/repo> --json headRefName`.
Run `git worktree list` for a worktree. Count review rounds from issue comments.

## BAD / GOOD

Expand Down
Loading