laravel:executing-plans
Executing Plans (Laravel)
Work in small batches. After each batch: tests green, quality clean, checkpoints recorded.
Loop
- Pick next small task
- Write failing test (feature or unit)
- Minimal implementation; commit
- Verify queues/events/IO if applicable
- Run Pint, static analysis, tests (parallel)
- Update docs/notes; checkpoint
Checkpoints
- Tests pass locally; no errors/warnings
- Pint clean; static analysis passes
- Migrations safe and idempotent; no breaking edits to merged migrations
- Queues healthy; Horizon metrics reasonable if used
- Feature branch notes updated (what changed, why)
Repeat until plan complete, then run laravel:quality-checks and request review.
More from jpcaparas/superpowers-laravel
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
89laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
89laravel:quality-checks
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
80laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
77laravel:eloquent-relationships
Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely
76laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
75