// PBI development pipeline — orchestrates design phase and impl+UT phase with sub-agent fan-out, file-based handoff, deterministic termination gates (Anthropic + Ralph + GAN-derived). Used by Developer per assigned PBI. Replaces former design + implementation skills.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | pbi-pipeline |
| description | PBI development pipeline — orchestrates design, impl+UT, PBI review, and UT-run stages with sub-agent fan-out, file-based handoff, and deterministic termination gates (Anthropic + Ralph + GAN-derived). Used by Developer per assigned PBI. Replaces former design + implementation skills. |
| disable-model-invocation | false |
pbi-designer,
pbi-implementer, pbi-ut-author, codex-design-reviewer,
codex-impl-reviewer, codex-ut-reviewer.scrum/scripts/commit-pbi.sh. Never commit directly
with raw git commit: a raw git commit -A would stage the
.scrum -> ../../../.scrum symlink that create-pbi-worktree.sh
installs, and that symlink would then propagate to main on the
per-PBI merge. commit-pbi.sh excludes the symlink via
git add -A -- ':!.scrum' and only it is safe.items[].status driven via
.scrum/scripts/update-backlog-status.sh (Developer manages the
in_progress_* range; SM owns the rest of the 12-value enum).in_progress_design → in_progress_impl ⇄ in_progress_pbi_review ⇄ in_progress_ut_run → in_progress_merge
→ escalated (any stage; via termination gate)
The 7 SM-managed status values (see docs/data-model.md § State Transitions: status) MUST NOT be written by this skill.
[Init] create .scrum/pbi/<pbi-id>/ + state.json (rounds, *_status)
update-backlog-status.sh "$PBI_ID" in_progress_design
↓
[Design Stage] Rounds 1..5 → see references/design-stage.md
- status: in_progress_design
↓ success
[Impl Stage] Rounds 1..5 → see references/impl-ut-stage.md
- status: in_progress_impl
- per round: spawn impl + UT in parallel
↓
[PBI Review Stage]
- status: in_progress_pbi_review
- codex-impl-reviewer + codex-ut-reviewer in parallel
- aggregate findings; FAIL → status reverts to in_progress_impl
(next impl round). See [feedback routing](references/feedback-routing.md)
for how findings/test failures are split between impl and UT agents.
↓ PASS
[UT Run Stage]
- status: in_progress_ut_run
- real test execution + coverage measurement → see references/coverage-gate.md
- aggregate Pass criteria; FAIL → status reverts to in_progress_impl
(next round) OR escalates (termination gate)
↓ PASS
[Ready-to-merge handoff]
- run .scrum/scripts/mark-pbi-ready-to-merge.sh <pbi-id>
(sets head_sha, paths_touched, ready_at; sets backlog status to
in_progress_merge)
- notify SM: "[<pbi-id>] PBI_READY_TO_MERGE branch=pbi/<id> sha=<head>"
- stop and wait for SM SendMessage (MERGED / MERGE_CONFLICT /
ARTIFACT_MISSING)
See references/sub-agent-prompts.md for full input prompt templates.
pbi-designer — Design Round Step 1 (sequential)codex-design-reviewer — Design Round Step 2 (sequential)pbi-implementer ‖ pbi-ut-author — Impl Round Step 1 (parallel pair)codex-impl-reviewer ‖ codex-ut-reviewer — PBI Review Stage (parallel pair)PBI internal state: .scrum/pbi/<pbi-id>/state.json (round counters,
per-stage *_status flags). Backlog status is the SSOT for stage
position; state.json holds internal mechanics only. See
references/state-management.md for schema and write helpers.
Catalog write contention: see references/catalog-contention.md
(3-layer defense: sprint planning pre-separation + flock + mtime check).
When a termination gate triggers escalation, set backlog status to
escalated via update-backlog-status.sh, write
escalation_reason into state.json via update-pbi-state.sh, and
notify SM via Agent Teams. SM handles via the
pbi-escalation-handler skill.
See termination gates for the composite gate matrix (success / stagnation / divergence / hard cap) evaluated at end of each Round.
items[].status ∈ {in_progress_merge, escalated}in_progress_merge: state.json.head_sha and paths_touched
populated, ready_at setescalated: state.json.escalation_reason populated