governance-validation

Validate governance constraints and architecture boundaries across SEA project changes.

1|Updated Oct 1, 2025

Search Tags:#architecture #compliance #governance #CALM #spec-guard #flow-lint

Ready to run

npx skills add https://github.com/GodSpeedAI/SEA --skill governance-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governance-validation
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/governance-validation
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill governance-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure governance constraints, CALM compliance, and architecture boundaries are consistently enforced across changes by orchestrating spec-guard, flow-lint, and CALM validations.

Core Features & Use Cases

Spec Validation: Validates SDS YAML schema compliance, SEA-DSL syntax validation, and cross-reference integrity.
Flow Lint: Enforces CQRS annotation requirements on all Flows.
CALM Architecture: Validates architecture definitions against CALM specifications.

Quick Start

Just run the following in sequence:

just spec-guard
just flow-lint
calm validate

Frequently Asked Questions about governance-validation

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

FAQPage Schema

How do I validate CALM architecture boundaries across project PRs?▼

To enforce CQRS annotation requirements on all Flows, run the just flow-lint command. This automated flow lint process validates that your SEA project changes maintain the required CQRS annotations across the workflow.

What is the best way to validate SDS YAML schema compliance?▼

The best way to validate SDS YAML schema compliance is running the just spec-guard command. This spec validation process checks SDS YAML schema, SEA-DSL syntax validation, and cross-reference integrity for your project changes.

Does governance validation work with automated code-generation workflows?▼

Governance validation works with automated code-generation workflows by orchestrating spec-guard, flow-lint, and CALM validations. It enforces invariants across these workflows and generates actionable remediation outputs for any violations found.

Why do I need to run spec-guard, flow-lint, and calm validate in sequence?▼

Running spec-guard, flow-lint, and calm validate in sequence ensures comprehensive governance validation by progressively checking schema compliance, CQRS flow annotations, and architecture boundaries. This sequence produces actionable remediation outputs for identified violations.