review-phase-level

Validate phase-level climate, geographic, and budget constraints with structured scores.

98|7|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Sea-Go/Sea-BreakTheWaves --skill review-phase-level
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-phase-level
Source: https://github.com/Sea-Go/Sea-BreakTheWaves/tree/main/agent_v2/skills/review-phase-level
Command: npx skills add https://github.com/Sea-Go/Sea-BreakTheWaves --skill review-phase-level

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Phase-level seasonal constraints are satisfied across climate, geography, and budget, helping planners avoid invalid phase configurations and misaligned resources.

Core Features & Use Cases

  • Climate validation: checks avgHighTemp and weather risk for all phase regions.
  • Geographic progression: enforces logical city-order without large backtracks within a phase.
  • Budget alignment: verifies Phase.estBudget and Phase.dayCount proportions against annual totals.
  • Soft constraints: flags seasonal coverage with soft notices.
  • Use Case: Scenario where a Phase must meet climate, distance, and budget constraints before approval.

Quick Start

Provide Phase node context to the validator and request a compliance score for the phase.

Frequently Asked Questions about review-phase-level

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate phase-level seasonal constraints for climate and budget planning?

Phase constraint validation analyzes climate compatibility, geographic progression, and budget distribution to assess phase-level feasibility. It checks average high temperatures, weather risks, city-order logic, and budget proportions against annual totals to return a structured compliance score with violations.

What is phase constraint validation and when do I need it for safe planning?

Phase constraint validation is a deterministic check of climate, geography, and budget alignment for a specific phase. You need it before phase approval to avoid invalid configurations, misaligned resources, and seasonal weather risks across your planned regions.

How do I check if my phase budget and day count proportions match annual totals?

Budget alignment verification compares your estimated phase budget and day count against annual totals to ensure proportional distribution. The validator enforces deterministic checks on these ratios and flags any budget misalignment in its remediation-focused output.

Can I use phase validation to enforce logical city-order progression without large backtracks?

Geographic progression validation enforces logical city-order within a phase to prevent large backtracks. By analyzing the sequence of phase regions, it determines if your route configuration meets distance constraints and returns violations for any illogical geographic jumps.

Does phase validation support soft constraints for seasonal event coverage?

Soft constraint checking flags seasonal coverage with soft notices rather than strict violations. This allows you to assess seasonal event compatibility and weather risks while maintaining deterministic enforcement for critical climate and budget constraints.

What limitations exist when validating weather constraints across multiple phase regions?

Validation focuses on average high temperatures and weather risk data for all phase regions but requires complete Phase node context. It provides deterministic checks and remediation-focused scores, meaning incomplete climate data or missing seasonal event context will limit the accuracy of the compliance assessment.