rule-laravel-shared-workflow-definition-model-decision

Enforce Laravel workflow governance using the central decision-model rule.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-workflow-definition-model-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-laravel-shared-workflow-definition-model-decision
Source: https://github.com/belluga/delphi-ai/tree/main/skills/rule-laravel-shared-workflow-definition-model-decision
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-workflow-definition-model-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governance gaps during creation or update of Laravel workflows are minimized by applying a central decision-model rule.

Core Features & Use Cases

  • Enforces using the shared workflow template scaffold, file naming in kebab-case, and required headers.
  • Ensures governance completeness by validating rule/workflow parity across canonical and Cline surfaces.
  • Supports end-to-end workflow definition with explicit gates and traceability from definition to delivery.

Quick Start

When defining or editing a Laravel workflow, apply this rule to anchor it to the template and establish governance gates.

Frequently Asked Questions about rule-laravel-shared-workflow-definition-model-decision

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

FAQPage Schema
How do I enforce consistent file naming and headers when scaffolding Laravel workflows?

Laravel workflow governance is enforced by applying a central decision-model rule that mandates kebab-case file names and required headers during workflow scaffolding. This anchors definitions to a shared template for structural consistency.

What is a shared workflow definition model in Laravel DevOps governance?

A shared workflow definition model is a canonical governance template that establishes parity across development surfaces. It provides explicit gates and traceability from workflow definition to delivery, minimizing governance gaps during updates.

How do I validate cross-surface governance gates for Laravel workflow definitions?

Cross-surface governance gates are validated by applying a decision-model rule that checks rule and workflow parity across canonical and Cline surfaces. This verifies compliance with plan-adherence constraints and template references.

Does this Laravel workflow governance rule apply to both creating and updating workflows?

Yes, the workflow governance rule applies to both creating and updating Laravel workflows. It enforces template scaffolding, file naming conventions, and rule linkage to maintain governance completeness throughout the lifecycle.

Why do my Laravel workflow definitions fail governance checks during scaffolding?

Workflow definitions fail governance checks when missing references to the central workflow template, violating kebab-case naming rules, or lacking required headers. The decision-model rule validates these constraints to prevent governance gaps.