rule-laravel-shared-todo-driven-execution-model-decision

Enforce tactical TODO gating before code changes in Laravel projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Rule ensures governance and alignment before any implementation changes, preventing drift and untracked work.

Core Features & Use Cases

  • Enforces tactical TODO gating before code/docs changes.
  • Validates module anchors and canonical coverage across delivery.
  • Generates a formal execution plan and baselines to ensure traceability.

Quick Start

Draft a tactical TODO file and secure APROVADO before starting any project changes.

Frequently Asked Questions about rule-laravel-shared-todo-driven-execution-model-decision

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

FAQPage Schema
How do I enforce execution plan gating before starting Laravel module changes?▼

Execution plan gating requires drafting a tactical TODO file and securing approval before starting any Laravel project changes. This prevents drift and untracked work by validating module anchors and canonical coverage across delivery.

What is tactical TODO gating for multi-module Laravel projects?▼

Tactical TODO gating is a governance mechanism requiring structured pre-implementation planning before code or documentation changes. It generates formal execution plans and baselines to ensure traceability across large, multi-module Laravel projects.

When do I need canonical coverage and module anchors for Laravel delivery?▼

You need canonical coverage and module anchors when managing large, multi-module Laravel projects requiring strict governance. These mechanisms ensure module coherence, decision baseline satisfaction, and evidence-backed planning for delivery.

How do I set up a decision baseline to prevent drift in Laravel projects?▼

Set up a decision baseline by drafting a tactical TODO file that defines gate criteria and module anchors. Secure approval before changes to enforce alignment, validate canonical coverage, and generate a formal execution plan for traceability.

Can I use this gating approach for small Laravel projects without multiple modules?▼

This gating approach targets large, multi-module Laravel projects requiring explicit gating, module anchors, and canonical decisions. Small projects without complex module interactions may not need this level of structured pre-implementation planning and traceability enforcement.

Why does untracked work happen without formal execution plans in Laravel development?▼

Untracked work occurs without formal execution plans due to lack of governance and alignment before implementation changes. Tactical TODO gating addresses this by applying gate criteria, validating module coherence, and securing decision baselines prior to delivery.