laravel-domain-delivery

Implements or reviews Laravel changes with explicit rollback discipline and verification.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill laravel-domain-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-domain-delivery
Source: https://github.com/vTRKA/supervibe/tree/main/skills/laravel-domain-delivery
Command: npx skills add https://github.com/vTRKA/supervibe --skill laravel-domain-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Laravel changes often become risky and hard to verify because authorization, persistence shape, async side effects, caching, and deploy sequencing can be mixed or implicitly assumed.

Core Features & Use Cases

  • Contract-first Laravel slice delivery: Keeps HTTP input, validation/authorization, Eloquent persistence, and orchestration in their framework-owned boundaries (Form Requests, Policies/Gates, models, services/actions, jobs/events, cache, migrations).
  • Production verification evidence: Requires scoped commands, explicit proof of query shape and behavior constraints, and durable “workflow receipts” before claiming completion.
  • Rollback discipline: Enforces reversible migrations or documented irreversible decisions, plus compatibility/feature-flag/queue-cache rollback plans for the changed slice.

Quick Start

Ask your AI to review and implement a small Laravel feature using Form Requests, Policies/Gates, Eloquent with proven query shape, focused tests, and a named rollback plan, and then run the required scoped verification command before final completion.

Frequently Asked Questions about laravel-domain-delivery

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

FAQPage Schema
How do I ensure my Laravel migrations include proper rollback plans and verification evidence?

To ensure Laravel migrations include rollback evidence, apply strict rollback discipline by enforcing reversible migrations or documenting irreversible decisions, and run scoped verification commands to prove query shape before completion.

What is the best way to structure Laravel Form Requests, policies, and Eloquent models for a safe feature delivery?

The best way to structure Laravel features is contract-first delivery, keeping HTTP input in Form Requests, authorization in policies, and persistence in Eloquent models within their framework-owned boundaries for verifiable modifications.

How do I manage cache consistency and async side effects when updating Laravel queues and jobs?

Managing Laravel queues and jobs requires inspecting the source-of-truth to verify cache consistency and async side effects, returning a BLOCKED or PARTIAL status to localize failures instead of guessing the queue state.

Does Laravel policy gate verification require explicit deployment sequencing before finalizing a feature slice?

Laravel policy gate verification requires explicit deployment sequencing and rollback planning, ensuring that authorization changes, feature flags, and cache interactions deliver stack-native, verifiable modifications.

Why does my Laravel feature implementation fail when combining persistence shape changes with queue side effects?

Laravel implementations fail when persistence shape and queue side effects are implicitly assumed, requiring source-of-truth inspection and bounded scope to deliver explicit failure localization rather than guessing.

When do I need to document irreversible migration decisions in a Laravel application?

You need to document irreversible migration decisions in Laravel when strict rollback discipline cannot enforce a reversible migration, ensuring the changed slice still has a compatibility or feature-flag rollback plan.