This skill should be used when managing risks, assumptions, clarifications, or dependencies. Triggers when adding new risks, updating risk status, identifying assumptions, or tracking open decisions.
From agile-lifecyclenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleThis skill uses the workspace's default tool permissions.
references/risk-patterns.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.
Risk management in this framework is a continuous, transversal activity. Risks are tracked in a risk register from Phase 1 onwards. Assumptions are documented and resolved or accepted. Clarifications represent open decisions that must be closed before phase completion. Dependencies on external parties are tracked separately. This skill provides the process for identifying, categorizing, and maintaining all four registers.
Determine whether the item is:
Use the appropriate template:
templates/transversal/risk-register-entry.md.templatetemplates/transversal/assumption-register-entry.md.templatetemplates/transversal/clarification-entry.md.templateFill all mandatory fields. For risks:
id: unique identifier (e.g., RISK-001)description: clear description of the risk event and its causecategory: technical | AI/data | organizational | commercial | complianceprobability: low | medium | high | criticalimpact: low | medium | high | criticalowner: named person responsible for managing the riskphase: current phase (1–7)mitigation: specific actions to reduce probability or impactcontingency: what to do if the risk materializesstatus: open | mitigated | accepted | closedCalculate the risk score using the probability × impact matrix in references/risk-patterns.md. Prioritize:
For risks rated Medium or above:
At each sprint review and phase gate:
For each assumption entry:
assumption: the statement believed to be true (e.g., "API latency will remain below 200ms")validation_method: how the assumption will be confirmed or refutedreview_date: when this assumption must be validatedowner: who is responsible for validating itFor each clarification entry:
question: the specific open decision or questioncontext: why this is blocking or criticalowner: who is responsible for resolving itdue_date: when it must be resolvedresolution: fill this when the decision is made
If a clarification is past its due date and unresolved: escalate to PM and flag as blocker.For projects with AI/ML components, apply the AI-specific risk patterns from references/risk-patterns.md:
references/risk-patterns.md — Risk categories, probability × impact matrix, mitigation templates, AI-specific patternsschemas/risk-register.schema.jsonschemas/assumption-register.schema.jsonschemas/clarification-log.schema.json