This skill should be used when enforcing compliance with a signed waterfall phase contract — checking mandatory fields, verifying exit criteria completeness before a gate review, and blocking gate requests when contract gaps are found. Distinct from the phase-contract skill (which creates contracts); this skill enforces them.
From waterfall-lifecyclenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin waterfall-lifecycleThis skill uses the workspace's default tool permissions.
references/contract-enforcement-rules.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.
A signed phase contract is the governance baseline for a waterfall phase. This skill performs pre-gate enforcement: it reads a signed contract, checks every mandatory field, verifies that all exit criteria are met or formally waived, and confirms that required evidence exists before a gate review is requested. The output is an enforcement report with a definitive gate readiness verdict — READY or BLOCKED. Without enforcement, contracts are documentation artefacts, not governance instruments.
Retrieve the signed phase contract document for the phase under review. Validate it against schemas/phase-contract.schema.json. Confirm the contract status field is set — if it is not_started, phase work has not formally begun and enforcement is premature.
Perform a hard check on all mandatory fields. FAIL immediately if any of the following are empty, null, or contain "TBD":
phase_id — must be a non-empty identifierphase_name — must be a non-empty stringstatus — must be a valid status valueowner — must be a named individual, not a team or role aliasstart_date — must be a valid ISO datetarget_end_date — must be a valid ISO dateentry_criteria — must contain at least one entryexit_criteria — must contain at least one entryevidence_required — must contain at least one specific artefact IDsign_off_authority — must be a named individual; "TBD" is an immediate FAILRecord PASS or FAIL per field. Any single FAIL blocks the gate verdict.
Review each entry criterion listed in the contract. The status of each entry criterion must not be not_assessed. If any entry criterion was never assessed before phase work started, log this as a process violation — it means the phase was started without meeting its own entry conditions.
This does not block the gate verdict on its own, but it must be recorded in the enforcement report as a finding.
For each exit criterion listed in the contract, check its current status:
met — acceptable; proceedwaived — acceptable only if Step 5 waiver validation passesnot_started — this is a BLOCK; phase has not addressed this criterionin_progress — this is a BLOCK; criterion is not complete at gate timeRecord every non-met and non-waived criterion as an exit criterion gap. Any exit criterion gap blocks the gate verdict.
For every exit criterion with status waived, verify all three of the following are present and non-empty:
waiver_justification — a written explanation of why the criterion is being waivedapprover_name — the name of the person who approved the waiver (must not be the phase owner self-approving; must be the sign_off_authority or their designated delegate)risk_acceptance_statement — a written statement acknowledging the risk of proceeding without this criterion being metA waiver missing any of these three fields is treated as invalid — the criterion reverts to requiring resolution before gate.
For each artefact ID listed in evidence_required:
Any artefact in evidence_required that cannot be found in the evidence index is an evidence gap. Evidence gaps block the gate verdict.
Produce a structured enforcement report with the following sections:
Mandatory Fields Status
| Field | Status | Notes |
|---|---|---|
| phase_id | PASS / FAIL | ... |
| ... | ... | ... |
Exit Criteria Gaps
List each criterion with status not_started or in_progress, with criterion text and current status.
Evidence Gaps
List each artefact ID in evidence_required that is not found in the evidence index.
Waiver Issues
List each waiver missing waiver_justification, approver_name, or risk_acceptance_statement.
Gate Readiness Verdict
READY — all mandatory fields pass, all exit criteria are met or validly waived, no evidence gapsBLOCKED — one or more blocking issues exist; list each blocking reason explicitlyDo not issue a READY verdict if any single blocking condition is present.
in_progress and not_started are not acceptable states.schemas/phase-contract.schema.jsonskills/phase-contract-enforcement/references/contract-enforcement-rules.md — Mandatory field matrix, exit criteria rules, common failures checklistreferences/gate-criteria-reference.md — What gate reviewers check and how enforcement output maps to gate criteriareferences/lifecycle-overview.md — Phase boundaries, sign-off authority roles, and escalation pathsnot_started or in_progress without a corresponding BLOCK verdict