| name | pmo-governance |
| description | Use for RAID, decisions, traceability, risk, policy checks, and Strict-mode guardrails. |
pmo-governance
Purpose
Maintain governance consistency without turning Lite projects into heavyweight programs.
Trigger
Use for risk triage, decision logging, RTM checks, approval policy, blocker handling, or Strict-mode escalation.
Required Inputs
PROJECT.md, relevant governance artifacts, and runtime config from pmo-config/context-map.json, pmo-config/policy.json, pmo-config/artifact-policy.json, pmo-config/reference-types.json, and pmo-config/validation-rules.json.
Allowed Context
Read only governance artifacts needed for the gate. Do not load archived skills.
Mode Behavior
Use pmo-config/artifact-policy.json for required/conditional/optional governance artifacts and pmo-config/policy.json for strict triggers, approval roles, and evidence values. Lite logs only material decisions/risks; Standard logs meaningful risk or business decision; Strict follows the configured governance artifact contract.
Execution Steps
- Classify risk and strict triggers.
- Check approval gates and evidence.
- Verify RTM coverage for Strict.
- Confirm config and docs do not drift.
Output Contract
Return risk status, required artifacts, missing evidence, and policy deviations.
Approval Rules
Human approval is required for scope, design where applicable, release, mode escalation, and production-sensitive decisions.
Validation Command
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/pmo-doctor.ps1
Prohibited Actions
Do not downgrade Strict triggers silently, fabricate decision evidence, hardcode artifact matrices, log every minor AI action, or approve on behalf of a human.
Completion Criteria
Governance artifacts match mode requirements and doctor/validator checks pass.