A scheduled pi session reads .pi/prompts/next-issue.md and works one open issue end to end: pick, claim, branch from origin/main, implement, verify on the tier the change demands, open a PR, stop.
It declines rather than improvises where it cannot verify itself — a busy :34115 means another worktree is running the app, and a green e2e run against someone else's build is worse than no run at all. It also treats a remote branch as a claim, since concurrent sessions in other worktrees do not always apply Status/In Progress.
This needs to be on main so that every branch cut from it carries the file: the scheduled job reads it by path, and a checkout that does not have it breaks every run after the first.
Verified: make skill-check (46 documented targets present), plus the pre-commit and pre-push suites.
A scheduled pi session reads `.pi/prompts/next-issue.md` and works one open issue end to end: pick, claim, branch from `origin/main`, implement, verify on the tier the change demands, open a PR, stop.
It declines rather than improvises where it cannot verify itself — a busy `:34115` means another worktree is running the app, and a green e2e run against someone else's build is worse than no run at all. It also treats a remote branch as a claim, since concurrent sessions in other worktrees do not always apply `Status/In Progress`.
This needs to be on `main` so that every branch cut from it carries the file: the scheduled job reads it by path, and a checkout that does not have it breaks every run after the first.
Verified: `make skill-check` (46 documented targets present), plus the pre-commit and pre-push suites.
logan
self-assigned this 2026-08-21 06:29:18 +00:00
A scheduled pi session reads this file and works one open issue end to
end: pick, claim, branch, implement, verify on the tier the change
demands, open a PR, stop. It declines rather than improvises where it
cannot verify itself — a busy :34115 means another worktree is running
the app, and a green e2e run against someone else's build is worse than
no run at all.
logan
merged commit 3871d37fdb into main2026-08-21 06:29:30 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A scheduled pi session reads
.pi/prompts/next-issue.mdand works one open issue end to end: pick, claim, branch fromorigin/main, implement, verify on the tier the change demands, open a PR, stop.It declines rather than improvises where it cannot verify itself — a busy
:34115means another worktree is running the app, and a green e2e run against someone else's build is worse than no run at all. It also treats a remote branch as a claim, since concurrent sessions in other worktrees do not always applyStatus/In Progress.This needs to be on
mainso that every branch cut from it carries the file: the scheduled job reads it by path, and a checkout that does not have it breaks every run after the first.Verified:
make skill-check(46 documented targets present), plus the pre-commit and pre-push suites.