pbi-pipeline

Orchestrate Product Backlog Item development through design, implementation, review, and validation.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill pbi-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbi-pipeline
Source: https://github.com/sohei56/maul-team/tree/main/skills/pbi-pipeline
Command: npx skills add https://github.com/sohei56/maul-team --skill pbi-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill coordinates the full development lifecycle for an assigned Product Backlog Item, preventing incomplete handoffs, unsafe commits, weak test coverage, and unresolved review findings from reaching the merge queue.

Core Features & Use Cases

  • End-to-End PBI Orchestration: Runs design, implementation, unit-test authoring, review, test execution, coverage validation, integrity review, and ready-to-merge handoff stages.
  • Multi-Agent Coordination: Fans work out to specialized designer, implementer, test-author, Codex reviewer, and integrity-reviewer agents with synchronous execution and file-based artifacts.
  • Deterministic Quality Gates: Enforces snapshot pins, worktree containment, coverage and acceptance-criteria test mapping, status transitions, retry limits, escalation rules, and safe PBI commits.
  • Use Case: When a Developer receives a backlog item, use this Skill to drive it from design through implementation and validation while routing failures back into bounded remediation rounds or escalating them to the Scrum Master.

Quick Start

Use the pbi-pipeline skill for the assigned PBI and provide its backlog entry, requirements path, related catalog specifications, and Scrum configuration.

Frequently Asked Questions about pbi-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Scrum development pipeline for Product Backlog Items?

Automate a Scrum development pipeline by orchestrating the complete PBI lifecycle from design and implementation to unit-test authoring, multi-agent review, coverage validation, and ready-to-merge handoff. This prevents incomplete handoffs and unsafe commits from reaching the merge queue.

What is multi-agent orchestration for code review and quality gates?

Multi-agent orchestration for code review fans work out to specialized designer, implementer, test-author, and reviewer agents with synchronous execution. It enforces deterministic quality gates like snapshot pins, coverage validation, and integrity assessments to ensure safe PBI commits.

How do I enforce test coverage validation and acceptance criteria mapping in a Scrum workflow?

Enforce test coverage validation by applying deterministic quality gates that check acceptance-criteria test mapping, worktree containment, and status transitions. Failures route back into bounded remediation rounds or escalate to the Scrum Master when retry limits are exceeded.

Can I use worktree isolation for safe PBI commits in a multi-agent development setup?

Yes, worktree isolation is supported for safe PBI commits in a multi-agent setup. The pipeline enforces worktree containment alongside pinned review snapshots and integrity assessments to ensure deterministic termination gates before any ready-to-merge handoff occurs.

Do I need Scrum state and backlog wrappers to run a PBI pipeline?

Yes, running a PBI pipeline requires Scrum state and backlog wrappers, specialized sub-agents, and Scrum configuration. You must provide the assigned backlog entry, requirements path, related catalog specifications, and configuration to start the end-to-end orchestration.

What is the best way to handle unresolved review findings before merging a Product Backlog Item?

Handle unresolved review findings by routing failures back into bounded remediation rounds with enforced retry limits. If issues persist, the pipeline escalates them to the Scrum Master, preventing unsafe commits with weak test coverage from reaching the merge queue.