ai4pb-init

Convert architecture backlog items into a runnable SCRUM sprint plan.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai4pb-init
Source: https://github.com/derekhu0002/ai4pb-orchestrator/tree/main/.opencode/skills/ai4pb-init
Command: npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The SCRUM flow skill automates the initialization of a sprint by translating architecture backlog items into a concrete, executable plan, reducing manual setup time and ensuring alignment with the architecture model.

Core Features & Use Cases

  • Automatic sprint kickoff: imports architecture backlog items and generates an initial task plan.
  • Phase-zero tagging & traceability: attaches sprint metadata to architecture elements and records iteration start points.
  • End-to-end workflow guidance: supports the Phase 0/Phase 1 process described in the architecture methodology and provides a reproducible kickoff.

Quick Start

Run the AI4PB kickoff to create an initial sprint plan from the architecture backlog in design.

Frequently Asked Questions about ai4pb-init

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

FAQPage Schema
How do I generate a sprint plan from an architecture backlog automatically?

Yes, you can automate sprint kickoff by importing architecture backlog items and applying view-resolution rules to generate an initial, executable SCRUM task plan with full architecture traceability.

What is architecture-driven sprint initialization in SCRUM?

Architecture-driven sprint initialization converts backlog items from SystemArchitecture.json into a runnable SCRUM plan. It enforces Phase 0 tagging and Phase 1 planning to maintain strict traceability to architecture elements.

How do I ensure traceability between sprint tasks and system architecture elements?

Traceability is ensured by attaching sprint metadata to architecture elements and recording iteration start points during Phase 0 tagging, linking executable tasks directly to the architecture model.

Can I use a fast task index to speed up sprint planning from a large architecture model?

Yes, a fast task index can be used alongside SystemArchitecture.json to accelerate sprint planning. The Skill applies view-resolution rules across these sources to assemble a coherent plan efficiently.

Do I need a specific SystemArchitecture.json file to start a model-driven sprint?

Yes, a design/KG/SystemArchitecture.json file containing your backlog items is required. It serves as the primary input for extracting tasks and executing the Phase 0 and Phase 1 planning workflow.

What are the limitations of using model-driven architecture for SCRUM task extraction?

Model-driven task extraction depends entirely on the structure of SystemArchitecture.json and strict adherence to Phase 0 and Phase 1 methodology. Poorly defined backlog items will result in incomplete or incoherent sprint plans.