Loop PBI

An agent skill for continuously implementing a PBI backlog with delegated AI agents: dependency-aware scheduling, small groups of related tasks, physical board transitions, validation, Git delivery, and worktree cleanup.

Install

npx skills add onlinedigital/loop-pbi --skill loop-pbi

For Codex, installed globally:

npx skills add onlinedigital/loop-pbi --skill loop-pbi --agent codex --global

All orchestration instructions, reference documentation, examples, script comments, and CLI messages are in English. Machine-readable results use JSON.

Use

Invoke $loop-pbi in your project to process its backlog. By default, it delegates to Codex 6.1-Sol with medium reasoning and commits/pushes each completed PBI. Override the model, reasoning, scope, or Git behavior in your request, for example:

$loop-pbi process only the documentation module, without push

The skill respects project instructions and discovers board/documentation paths instead of assuming specific folder names. Related, lightweight PBIs can share a single delegated agent and worktree; each PBI retains its own acceptance checks, evidence, lifecycle, and delivery.

Installing or reading the skill does not start implementation. Invoking it for execution authorizes the selected backlog workflow, including commit/push by default; specify without push when appropriate.

Included Bun CLI

Requires Bun. No npm dependencies. Worktree/history commands require Git; project validators retain their own runtime requirements. Run the CLI from the installed skill directory or this repository:

bun scripts/loop-pbi.ts --help
bun scripts/loop-pbi.ts scan --root /path/to/project
bun scripts/loop-pbi.ts ready --root /path/to/project
bun scripts/loop-pbi.ts validate --root /path/to/project
bun scripts/loop-pbi.ts claim 023 --agent vehicles-lite-01 --root /path/to/project
bun scripts/loop-pbi.ts finish 023 --evidence evidence/023.json --root /path/to/project --allow-project-commands
bun scripts/loop-pbi.ts worktree create vehicles-lite-01 --root /path/to/project
bun scripts/loop-pbi.ts history 023 --root /path/to/project

• claim assigns ownership and physically moves To Do → In Progress.
• finish executes evidence checks and project validators, moves the task to Done, and rolls back the lifecycle transition if final validation fails.
• Project-defined commands are disabled by default. Review configuration/evidence commands and their scripts before passing --allow-project-commands; the flag is an execution opt-in, not a sandbox. Internal board validation needs no external script or PowerShell.
• Worktrees live under .worktrees/<assignment>, with .worktrees/* added to .gitignore.
• The orchestrator cleans up each completed delegation after integration, required push, and agent shutdown. The CLI refuses dirty or unintegrated worktree removal; branch deletion uses ordinary git branch -d.
• Git trailers make each PBI searchable without a duplicate changelog database.

Read CLI configuration and behavior and Git history conventions before running mutating commands. The CLI accepts a deliberate subset of Markdown/YAML frontmatter, not arbitrary YAML. Field/folder mappings and explicit dependency overrides support different board conventions. Unknown dependency syntax is rejected rather than treated as empty.

Delegation and checkout behavior

An orchestration runtime must support the chosen provider/model. T3-specific guidance is included, but the workflow also supports native delegation where available. A nested worktree does not automatically change a child agent's thread binding: the child must use the assigned absolute cwd/workdir for every operation. Shared-checkout ownership is the fallback when explicit worktree operations are unsupported.

Tests

bun test scripts/loop-pbi.test.ts

Tests use isolated temporary repositories, covering dependency validation, concurrent claims, physical transitions, failed-validation rollback, shared worktrees for multiple PBIs, cleanup protections, and refusal to execute project commands without explicit opt-in.

Progress overview

The skill discovers the project's existing backlog overview and keeps a module progress table as its first visible content, before any title. The Bun helper calculates Done/total counts and Markdown bars; configured claim/finish transitions refresh it automatically. Run overview to refresh after manual board edits. Custom overview paths, module fields, phase fields, and task-to-module mappings are documented in the CLI reference.

Discoverability on skills.sh

The official FAQ explains that skills are listed through installation telemetry from the skills CLI. Public GitHub availability and installability are immediate; leaderboard indexing is controlled by skills.sh and may not be immediate.