[Change] SAFe PI Planning Essentials (WSJF + PI artifacts) — Δ5

[djm81]

Why

SAFe teams operate at PI/iteration/ART level. Today nold-ai/specfact-cli#116 (E4) includes ROAM list seed and #160 mentions SAFe usage, but there is no PI-level first-class support: no backlog pi-summary, no WSJF workflow, no PI readiness policy. Without .specfact/safe.yaml and PI artifacts, SAFe is an afterthought, not a supported framework.

What Changes

• Add CLI command specfact backlog pi-summary for PI-level summary: PI scope, team commitments, cross-team dependency contracts, ROAM items (when available from Add backlog dependency analysis and command suites specfact-cli#116).
• Config .specfact/safe.yaml for PI/iteration/ART settings; integrate with Policy Engine (feat(openspec): code review bug-finding and sidecar venv fix #176) for PI readiness policy hooks.
• WSJF assistance: calculation with AI-assisted missing-field proposals and confirmation; output as JSON and Markdown.
• Policy Engine (feat(openspec): code review bug-finding and sidecar venv fix #176) supports PI readiness policy when safe config is present.
• Dependency analysis ([Change] Spec-Kit Change Proposal Bridge & Backlog Extension Sync #116) cross-team dependency contracts and ROAM seed feed PI summary.
• Documentation (agile-scrum-workflows) for SAFe PI and WSJF.

Acceptance Criteria

• specfact backlog pi-summary outputs PI scope, commitments, dependency contracts, ROAM when available; JSON and Markdown.
• .specfact/safe.yaml supports PI/iteration/ART; Policy Engine PI readiness hook.
• WSJF assistance: calculation + AI-assisted missing fields + confirmation; no silent write.
• Docs updated (agile-scrum-workflows).

---

OpenSpec Change Proposal: safe-pi-planning