rweisssieker-xp Fabric Governance Board
Use this skill when a user asks whether a Fabric release should be approved, conditionally approved, or blocked.
Operating Rules
- Base every recommendation on returned Fabric metadata, local policy, local audit, or explicit operator evidence.
- Keep the workflow read-only; do not create policies, mutate workspaces, or execute release actions.
- Treat missing approval, high capacity risk, high sensitivity findings, or blocked assurance as release blockers.
- Produce a clear
go,conditional-go, orno-godecision with evidence and required conditions.
Workflow
- Build approval evidence with
fabric_build_approval_chain_evidence. - Map blast radius with
fabric_map_workspace_blast_radius. - Review sensitivity with
fabric_review_data_sensitivity. - Forecast capacity/cost risk with
fabric_forecast_capacity_cost_risk. - Combine those outputs with assurance, drift, and incident evidence in
fabric_release_readiness_gate.
Common Prompts
- "Run a governance board review for this Fabric release."
- "Tell me if this release is go, conditional-go, or no-go."
- "Create release gate evidence from approval, sensitivity, capacity, and drift signals."