From pdm-agile-delivery
Facilitate or prepare for a Program Increment (PI) Planning event in SAFe environments — aligning multiple Agile Release Trains (ARTs) around shared objectives.
npx claudepluginhub devmuslim/pdm-skills --plugin pdm-agile-deliveryThis skill uses the workspace's default tool permissions.
Facilitate or prepare for a Program Increment (PI) Planning event in SAFe environments — aligning multiple Agile Release Trains (ARTs) around shared objectives.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
Facilitate or prepare for a Program Increment (PI) Planning event in SAFe environments — aligning multiple Agile Release Trains (ARTs) around shared objectives.
A Program Increment is a 8–12 week delivery cycle (typically 4–5 sprints) used in SAFe. PI Planning is the face-to-face (or virtual) event where all teams plan together.
Day 1
Day 2
Classify PI-level risks:
| Risk | Classification | Action |
|---|---|---|
| API not ready from Team B | Resolved | Team B commits to Sprint 2 delivery |
| Vendor contract not signed | Owned | PDM tracks weekly, escalates if unsigned by Sprint 1 |
| Regulatory approval unclear | Accepted | Business accepts risk and monitors |
| Dependency on legacy system | Mitigated | Architecture team adds spike in Sprint 1 |
Per team:
Team votes 1–5 on confidence in delivering PI objectives:
/milestone-plan or /dependency-map