wave-coherence-validation

Analyze branches to enforce dependency ordering for wave tasks.

Updated Jan 19, 2026

Search Tags:#branch-management #dependency-analysis #API-contracts #wave-coherence #architecture-validation #frontend-backend-consistency

Ready to run

npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill wave-coherence-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wave-coherence-validation
Source: https://github.com/onshoreoutsourcing/lighthouse-beacon/tree/main/.claude/skills/wave-coherence-validation
Command: npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill wave-coherence-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that wave tasks are implemented in the correct dependency order by analyzing current and parent branches, detecting logical dependencies (database → API → UI), and surfacing blockers early to prevent rework.

Core Features & Use Cases

Dependency sequencing: validates the proper order from database migrations to API endpoints to UI components.
Cross-layer detection: identifies mismatches between layers (schema vs API shape vs frontend expectations) and flags blockers.
Artifact generation: produces a dependency graph and actionable next steps to guide implementation.
Use Case: Before starting a wave, run this skill to confirm all prerequisites are in place and no blockers remain.

Quick Start

Run the wave coherence validation on the active feature branch using the provided scripts.

Frequently Asked Questions about wave-coherence-validation

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

FAQPage Schema

How do I enforce correct dependency ordering for wave tasks to prevent out-of-sequence implementations?▼

You can enforce correct dependency ordering by analyzing current and parent branches to detect cross-layer dependencies, surfacing blockers until prerequisite work is complete. This ensures API contracts, data models, and UI integration follow a coherent sequence.

Why does my frontend backend consistency break when implementing wave tasks across multiple layers?▼

Frontend backend consistency breaks when cross-layer dependencies go undetected between schema, API shape, and frontend expectations. Analyzing branch dependencies identifies these mismatches early and flags blockers before implementation begins.

What's the best way to validate API contracts and data models before starting UI integration?▼

The best way to validate API contracts is running a dependency analysis on your active feature branch to confirm database migrations and API endpoints are complete. This surfaces actionable next steps and generates a dependency graph guiding implementation.

Can I detect cross-layer dependency mismatches between database migrations and API endpoints before implementation?▼

Yes, cross-layer detection analyzes current and parent branches to identify mismatches between database schema, API shape, and frontend expectations. It flags blockers and documents actionable steps for resolution before you proceed.

When do I need to run architecture validation for branch management and dependency sequencing?▼

You need architecture validation before starting a wave to confirm all prerequisites are in place and no blockers remain. Running dependency analysis ensures tasks build from database to API to UI in the correct sequence.

Does wave coherence validation work without external dependencies or installed packages?▼

Yes, wave coherence validation operates using provided scripts and references with no external dependencies. It analyzes branches and generates dependency graphs independently to surface blockers and guide implementation ordering.