This skill should be used when creating a new phase contract at the start of a phase, validating entry criteria before phase work begins, tracking exit criteria progress during a phase, or triggering a gate review when all exit criteria are met. This skill creates and maintains phase contracts; for tracking deviations from an already-signed contract, use phase-contract-enforcement instead.
From agile-lifecyclenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleThis skill uses the workspace's default tool permissions.
references/contract-structure.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 phase contract is the operational agreement that governs a lifecycle phase. It defines the mandatory conditions for entering and exiting a phase, the evidence required to prove completion, and the sign-off authority responsible for approval. Without a valid phase contract, a phase cannot be formally started or closed.
Determine which phase (1–7) is being contracted. Load the phase essentials card from docs/phase-essentials/phase-N.md. Review references/lifecycle-overview.md for entry/exit criteria specific to the phase.
Open the phase contract template (if available) or create the document with these mandatory fields:
phase_id: integer 1–7phase_name: canonical phase namestatus: one of not_started | in_progress | blocked | ready_for_review | ready_for_gate | approved | closedowner: accountable role or personstart_date: ISO date when phase was formally openedtarget_end_date: planned completion dateentry_criteria: list of conditions that must be TRUE before work startsexit_criteria: list of conditions that must be TRUE before gate reviewevidence_required: list of artefact IDs or evidence entries proving completionsign_off_authority: role responsible for approving phase completionBefore proceeding with phase work, document:
For each entry criterion, assess:
During the phase, regularly assess exit criteria:
not_started | in_progress | met | waivedmet or waived before triggering the gate reviewBefore requesting gate review:
references/artefact-catalog.md)When all exit criteria are met:
ready_for_gatereferences/lifecycle-overview.md — Phase context, entry/exit criteria per phasedocs/phase-essentials/phase-N.md — 1-pager per phase (start here)schemas/phase-contract.schema.jsonlifecycle-state.json